Android apps ready for the 64-bit requirement!

64-bit CPUs bring in areas such as artificial intelligence, machine learning, and immersive mobile. Supporting 64-bit prepares the ecosystem for the innovation enabled by the advanced compute capabilities of 64-bit devices, and for future Android devices that only support 64-bit code.

Starting August 1, 2019, all new apps and app updates that include native code must have 64-bit versions as well as 32-bit versions when publishing to Google Play.

How am I affected? Your app makes use of native code if it meets any of the following criteria:

- Your app makes use of C or C++ code.
- Your app links with third-party libraries that contain native code.
- Your app is built by a third-party app builder that uses native libraries.

Preparing for the 64-bit requirement

1. Inspect your APK or app bundle for native code. You can check for .so files using APK Analyzer. Identify whether they are built from your own code or are imported by an SDK or library that you are using. If you do not have any .so files in your APK, you are already 64-bit compliant.

The simplest way to check for 64-bit libraries is to inspect the structure of your APK file.
List down libraries from 32 bit
List down libraries from 64 bit

Platform 32-bit libraries folder
x86 lib/x86
lib/armeabi-v7a

64-bit libraries folder
lib/x86_64x
lib/arm64-v8a

For the ARM architecture, the 32-bit libraries are located in armeabi-v7a. The 64-bit equivalent is arm64-v8a.

For the x86 architecture, look for x86 for 32-bit and x86_64 for 64-bit.

The first thing to do is ensure that you have native libraries in both of these folders.

Count should be exactly equal then your app is compatible to 64. Many apps are written entirely in non-native code(e.g. the Java programming language or Kotlin) and do not need code changes. If not

2. Enable 64-bit architectures and rebuild native code (.so files) imported by your own code. See the documentation for more details.
Follow the link: https://developer.android.com/distribute/best-practices/develop/64-bit

Upgrade any SDKs and libraries to 64-bit compliant versions, if needed. Reach out to the SDK or library owner if one is not available. Google is working with top library owners on their 64-bit compatibility.

3. Test for issues locally once you’ve rebuilt your app.
How to check if your Android phone or tablet is 32-bit or 64-bit
Check Android kernel version. Go to 'Settings' > 'System' and check 'Kernel version'. If the code inside contains 'x64′ string, your device has a 64-bit OS; if you cannot find this string, then is 32-bit.

4. Rollout to your app for testing.

Extensions: Google Play will continue to accept 32-bit only updates to existing games that use the following SDKs:

Corona Labs SDK - until August 2020
Adobe Air software and the AIR SDK - until August 2020
Unity 5.6.7 or older - until August 2021
This ruling applies to apps written in C or C++ code or apps with links to third-party native libraries, for example. It does not apply to the many apps written in Java or Kotlin.

Starting August 1, 2021:

Google Play will stop serving apps without 64-bit versions on 64-bit capable devices, meaning they will no longer be available in the Play Store on those devices.
This will include games built with Unity 5.6.x or older.

Preparing for the 64-bit requirement
APKs or app bundles explicitly targeting Wear OS or Android TV, which are form factors that do not currently support 64-bit code.
APKs or app bundles that are not distributed to devices running Android 9 Pie or later.

Reference:

https://developer.android.com/distribute/best-practices/develop/64-bit