" [Action Required]: Create a 64-bit version of your app(s) by Aug 1, 2019 "

We received the following email from google play:

By August 1, 2019, all apps that use native code must provide a 64-bit version in addition to the 32-bit version in order to publish an update. This past January, we reiterated https://www.google.com/appserve/mkt/p/AFnwnKWnBHttIKBTnAnHNu7jVisNhmu7fiLsyouk4RAWac6Bl6fMN8cYXIEfPUdBNIWe-mtcrgtiEWdyqQC5YqfXZIosOTcXg0dUfLAAUYLblYJ7zkpPLPdQKthArGRoeGVlXWRfA50qm3xugUl29mROzBjBXSl26jyn20Hn9Vsu5d9HdQKUYWEL5A that this is required in order to make way for innovation and in anticipation of future Android devices that only support 64-bit code.

As the deadline approaches, we wanted to remind you that at least one of your apps* uses native code but does not currently offer a 64-bit variant:

OpenMRS Android Client

Action required:

  1. Please review all of your apps for 64-bit compliance. The Android developers guide https://www.google.com/appserve/mkt/p/AFnwnKXVrVoCRMDDw013BOlrkB8NSp8KaX-8XmO13SGcD2D0_Ex1tkqY_zSl215jdHRp26ArVdbj4aHwggfVD7NvzprUTZutB7qi-oKZauzCkXebqRZnhSIruDTitI9TmH0bruByaSsOU_G8s8lAvrD6KtNzMYSGpOq5yt7jaPiQyjXpMHutFcGg provides step-by-step instructions for assessing the use of native code and becoming 64-bit compliant, including identifying native libraries, building with 64-bit libraries, testing and publishing. Soon, the Play Console will also alert you when publishing if your app is not 64-bit compliant.

  2. To help us better understand your plans for compliance (and to let us know about any obstacles), please complete this optional 64-bit migration survey https://www.google.com/appserve/mkt/p/AFnwnKWGHXzTBz5vmbFmxUpl0Mxvzqf5ZHErHsTiIsr4TL9O9fds73BNny_Gj-iqV4Vz3j0y84U3yTPwFPZcPCEzubPkqghS85P_j_qYXaJGHFHIPC2q60zZ3z0ZfiSkzpP0ZXOD-wpdVAbEfLGA9xQKSb8q4jOIZLzaoU2hMajlthmzlpI-XmXIqcfKg5kzNlxQbAINNI7GBUl9qXAY.

Please note that we are not making changes to our policy on 32-bit support. Google Play will continue to deliver apps with 32-bit native code to 32-bit devices. The requirement means that those apps will need to have a 64-bit version as well.

If you have any questions or concerns, please contact Google Play developer support https://www.google.com/appserve/mkt/p/AFnwnKXv3rlnQ2GQIzAjaN9ld5ZqvaaYwTp0Cfe1t6KYuiuNOGPFp8iaBVJU7oXY_ElN5LvtzPih-npiG-5nmM7YdLod_aWkgpBwHc3CaWCQS2UBh9x9KYboqpoTZyTD1O7fMHilMtZD4c7qieFGLLpvzLvHPKWHc43MHsXRm8U7O41D9SEdBh9tGjLkORo.


The Google Play team

*Note: This list of apps reflects Google’s best estimate as of 16/05/2019. Only the top apps in your account are listed. This list should not be considered exhaustive. We encourage you to review ALL of your apps for native code and make sure 64-bit variants are offered where necessary.

Does that affect us at all? Do we need to do anything?


surely we have work to do @cintiadr

@f4ww4z did you see this? :slight_smile:

Hi @cintiadr , the notice is meant for apps that use native code (C / C++ code) or native libraries, if an app doesn’t use it then it is already considered 64-bit compliant. I’ve just analyzed the Android client’s latest APK and I have not found any native code. I think that we should be good to go.

I dont understand as it seems there’s no .so files in the APK. See the APK structure:

@deepak140596 can you confirm this?

Thanks for the reminder @cintiadr @dkayiwa

1 Like

I can also confirm that there are no .so files in our app. I think we are fine.

1 Like

@cintiadr We have found the cause - it’s due to one of our dependencies using native code. @deepak140596 (GSoC '19 student for the Android client) is working on it at https://issues.openmrs.org/browse/AC-606 .