PeerPlay
If Play Console says your app doesn't support 16 KB memory page sizes, the problem is in native code: one or more .so libraries in your bundle were built for 4 KB pages. Rebuild with up to date tools and libraries so every native library is 16 KB aligned, then upload the new bundle.
Google announced that new apps and updates targeting Android 15 or higher must support 16 KB page sizes on 64-bit devices, with the deadline in late 2025. Check the current wording in Play Console for your app, because Google has given some developers extra time on request. In practice, many developers now meet this warning while uploading builds for closed testing.
Does it affect your app at all?
Only apps with native code are affected. If your app is written only in Kotlin or Java and doesn't include any .so files, it already works on 16 KB devices and you don't need to change anything.
Native code often comes in without you noticing. Flutter, React Native, Unity and most game engines ship native libraries, and so do many SDKs for ads, analytics, image processing, databases and video. To see what you have, open your bundle in Android Studio with Build, Analyze APK and look in the lib folder.
How to check if your bundle is compliant
Play Console shows the status per bundle. Open App bundle explorer, pick the bundle and look for the memory page size information there. This is the quickest check, because it is what Google itself uses.
In Android Studio, APK Analyzer marks native libraries that aren't 16 KB aligned. On the command line, zipalign -c -P 16 -v 4 followed by your APK path checks the alignment of an APK built from the bundle.
To test the app itself, Android Studio offers emulator system images with a 16 KB page size for Android 15 and newer. Run your app on one and go through the main screens. A library that isn't ready often crashes at startup.
What to change for native Android code
Update the Android Gradle Plugin to a recent version. Newer versions package uncompressed native libraries with 16 KB zip alignment for you.
If you compile C or C++ with the NDK, update to NDK r28 or newer, which builds 16 KB aligned libraries by default. On older NDK versions you can add the linker flag -Wl,-z,max-page-size=16384, but upgrading is the cleaner fix.
For prebuilt .so files you don't compile yourself, you need a new version from whoever made them. You can't fix the alignment of someone else's library after the fact.
Flutter, React Native, Unity and third-party SDKs
For cross-platform apps the fix is usually an upgrade. Recent releases of Flutter, React Native and Unity build 16 KB compatible apps, so move to a current stable version of your framework and rebuild. Check your framework's release notes for the exact minimum version, because it changed over 2025.
Plugins and packages count too. A Flutter plugin or React Native library with its own native code needs to be updated separately. If one of them has no compatible version, look for a maintained alternative or ask its maintainer.
After every upgrade, run the App bundle explorer check again. One old library is enough to keep the warning.
Don't let it stall your closed test
If you are in the middle of a 14-day closed test, uploading a fixed build is fine. Opted-in testers get the update through the Play Store, and what counts for the requirement is that 12 or more of them stay opted in every day.
If you need those testers, PeerPlay is a free way to find them. Android developers test each other's apps every day through your real closed track, on real phones, which is also a good way to catch a native library that crashes on some devices.
FAQ
Does the 16 KB page size requirement affect Kotlin-only apps?
No. It only affects apps that include native libraries, the .so files in the lib folder of your bundle.
How do I check if my app supports 16 KB page sizes?
Open the bundle in App bundle explorer in Play Console, or use APK Analyzer in Android Studio, which flags native libraries that aren't 16 KB aligned.
Which NDK version builds 16 KB aligned libraries?
NDK r28 and newer do it by default. Older versions need the linker flag -Wl,-z,max-page-size=16384.
What if a third-party SDK isn't 16 KB compatible?
Update it to its latest version. If no compatible version exists, you need a replacement, because you can't realign a prebuilt library yourself.