Hi Everyone,
For some time now Google play store has been warning me that the APK that I uploaded to the play store is requiring a 64-bit version in addition to the 32-bit version when publishing to Google Play. They have granted an extension to me but the date for this is February 1, 2020. After February 1st, the extension will expire they are saying I will be unable to roll out non-compliant releases.
I tried looking in to this in matter on the forum and Paul posted a reply to somebody to say that the AppGameKit - APK files are 32bit and 64bit compatible already and have been for some time.
I'm hoping is Google's software flagging up a false positive but Google really seems to think there is a problem with my app in this regard and I'm quite worried as in the past few months my App has had 17K downloads and is making me a fair amount of income from subscriptions.
The APK for my app was built with AGK2 classic tier 1 I'm wondering as because I now have AppGameKit studio if I generate the APK with that and do an update if this might help and get Google off my back about it?
Does anybody have any information or advice in this regard and is anybody else getting these warnings from the play store?
By the way thanks so much to the creators and developers of App Game Kit and The Game Creators I don't think I would have ever been in the position to have created an App and had it live on the play store in the first place.
I have included the email Google sent below in case you're interested.
Thanks for any advice in advance
Matt
Hello Google Play Developer,
In August 2019, we began requiring all apps using native code to provide a 64-bit version in addition to the 32-bit version when publishing to Google Play. One or more of your apps was granted a six-month extension until February 1, 2020.
Action required
Please review all of your apps for 64-bit compliance. After February 1st, the extension will expire and you will be unable to roll out non-compliant releases. No additional extensions will be granted.
Affected apps
As of January 6, 2020, we have detected the following app(s)* were not compliant:
com.football_tip_app.my_app
Assessing 64-bit compliance
If you’re not sure whether your app fully supports 64-bit, you can check your compliance status by reviewing your release history or by uploading a draft version to the Play Console. You’ll see an alert if there’s anything to address.
The Android developers guide also provides step-by-step instructions for assessing the use of native code and becoming 64-bit compliant. The following are common reasons why an app may not be 64-bit compliant:
• Architecture compliance. For each native 32-bit architecture you support, you must include the corresponding 64-bit architecture.
o For the ARM architecture, the 32-bit libraries are located in armeabi-v7a. The 64-bit equivalent is arm64-v8a.
o For the x86 architecture, the 32-bit libraries are located in x86. The 64-bit equivalent is x86_64.
• Multi-apk compliance. If you use multi-apk, ALL apks in the release which support Android Pie or later must offer 64-bit variants. For further detail, please see this guidance on ensuring compliance.
• Legacy Renderscript (.bc) files. The Android platform will force any .apk containing .bc files to run in 32-bit, even if it supports 64-bit. In this situation, developers should remove the .bc files and rebuild the app using build tools 21 or later.
If you have any questions or concerns, please contact Google Play developer support or your business development representative.
* Note: This list of apps reflects Google’s best estimate as of the sending of this email. 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.
