Fix: "Your app doesn’t support 16 KB memory page sizes"
What triggers it, the official deadline, and the fix by stack. Sources checked 2026-10-02.
| Google source | Quote |
|---|---|
| Page sizes support guide | “All apps targeting Android 15 (API level 35) and higher must support 16 KB memory page sizes on 64-bit devices on Google Play. Starting February 1, 2027, if your app updates don't support 16 KB memory page sizes, you won't be able to release these updates.” |
Fix by stack
Flutter
We measured this directly: the Flutter engine shipped 4 KB-aligned native code through 3.15.x and newer, and is aligned from 3.16.0 on (evidence and Gradle line). Upgrade your Flutter SDK, not a Gradle dependency — libflutter.so comes from the engine build.
React Native / Expo
We measured this directly: com.facebook.react:react-android and com.facebook.react:hermes-android are both aligned from 0.77.0 on (react-android evidence, hermes-android evidence). Expo apps on a current SDK pull these transitively — check your resolved RN version with ./gradlew :app:dependencyInsight.
Unity
Unity’s own native player libraries (libunity.so, libil2cpp.so) aren’t in our measured 80+ library dataset yet, so we can’t give you a version boundary here. Run the free checker directly on your built APK/AAB (below) and see Unity’s own compatibility notes and Google’s build-in-Unity guide.
Not sure which of these applies to you? All four Google Play native-code deadlines are on one page, and the free dependency checker or check16k.py will tell you if 16 KB alignment specifically is your problem.
The paid kit ($12, v2.1) contains the complete measured fix map for all 80+ libraries as JSON and a table, every raw per-version measurement, the spot-check evidence, and the CI checker. This page and the checker script stay free.
Get the kit ($12)Full refund within 14 days if the kit didn't help you find or fix your blocker, no questions — email us and we process it via Polar's Refunds API.