Articles

Google Play's 16 KB Page Size and Target API Rules, Explained for App Owners

Google Play refuses app updates whose native libraries don't support 16 KB memory pages, or that target an older Android version than it allows. The fix is usually not a build setting but an upgrade of the framework the app is built on. For React Native that means version 0.77 or later for 16 KB support, and for an Expo app targeting Android 16 (API 36) it means Expo SDK 54 with React Native 0.81. Here is what both rules mean, how to check an app yourself, and how we brought a live app back into compliance.

By UPGRADEPublished

What the problem looks like

In August 2026 Google Play refused an update to Salwa, a grocery app we maintain, with one line: “Your app does not support 16 KB memory page sizes.” Of the 46 native libraries in its 64-bit builds, 44 were aligned to 4 KB. The version already live on Play contained the same 44 libraries. Nothing in the app had changed. Google had simply started enforcing the rule, so an app that updated without trouble one month could be refused the next.

The second rule shows up as a warning in Play Console about your app's “highest non-compliant target API level”. It can appear even when the production version is compliant, for a reason explained below.

What 16 KB memory pages are

Android has always managed memory in 4 KB pages. Newer devices can use 16 KB pages, which Google says makes apps start faster and use power more efficiently. On those devices a native library, a compiled .so file inside the app, can only load if it was built with 16 KB alignment. Google Play therefore requires apps that target Android 15 or later to ship 16 KB-aligned native code.

Apps written purely in Kotlin or Java with no native libraries are usually unaffected. Apps with native code are affected, and that includes React Native and Flutter apps, games built on engines, and many third-party SDKs.

Why a build setting usually doesn't fix it

Libraries you compile yourself can be fixed in the build: recent versions of Android's native toolchain (NDK r28 and later) align to 16 KB by default, and older ones accept a linker flag. But most of the native code in a React Native app is prebuilt, compiled by the framework's maintainers and downloaded as finished binaries: libreactnative.so, libhermes.so, libjsi.so, libc++_shared.so and the Fresco image libraries. No setting in your project can change how those were linked. The only fix is to upgrade to versions that were built with 16 KB alignment. React Native added it in 0.77, and Expo in SDK 53 (53.0.14 and later).

We also tested three fixes often suggested online, and none of them worked. Turning on React Native's new architecture has nothing to do with page size. The CMake flag ANDROID_SUPPORT_FLEXIBLE_PAGE_SIZES only affects libraries your project compiles itself. And the payment SDK some people blamed ships no prebuilt native code at all.

How to check your own app

Check the built file, not the project configuration. One of our builds had every setting right and still contained 44 misaligned libraries. Three ways to check, from easiest to most thorough:

  • Open the .apk or .aab in Android Studio's APK Analyzer, which flags libraries that are not 16 KB aligned
  • Run zipalign -c -P 16 -v 4 on the APK to check how the libraries are aligned inside the archive
  • Unzip the bundle and run readelf -l (or llvm-readelf -l) on each .so: every LOAD segment's alignment must be 0x4000 (16384) or more
  • Judge only the 64-bit folders (arm64-v8a and x86_64); 32-bit libraries are exempt

The target API rule

Every year Google raises the Android version that new apps and app updates must target. From 31 August 2026 that is Android 16 (API 36). Existing apps that are not updated must target at least Android 15 (API 35) to stay available to new users on newer Android versions. Only apps targeting API 34 or lower are flagged in 2026.

Raising the target changes how the app behaves, so it is not a one-line change. Apps that target Android 15 draw edge to edge, behind the status and navigation bars, and Android 16 removes the option to opt out. Android 16 also ignores portrait-only and fixed-size settings on screens 600dp wide or more, so the app will rotate on tablets and unfolded foldables. For React Native, targeting API 36 needs Android Gradle Plugin 8.9.1 or later. React Native 0.76 shipped 8.6.0 and React Native 0.81 ships 8.11.0, which in an Expo app means SDK 54.

The trap: old builds sitting in testing tracks

Google Play judges every build that is active in any track, not just production. A testing track keeps its last release indefinitely, so an internal or closed track you haven't touched for a year can still hold an old build that targets an old API. That is how Salwa showed a target-API warning while production was already on API 36: the alpha and internal tracks still served builds from an earlier version that targeted API 34.

Play Console has no delete button for a release, a build or a track. The only way to clear an old build is to publish a newer version code to that track. And if you manage tracks through the API, be aware that sending an empty release list returns success and changes nothing. Re-read the tracks afterwards to confirm.

How we fixed it on a live app

For Salwa the fix was an upgrade to Expo SDK 54: React 18.3.1 to 19.1.0 and React Native 0.76.9 to 0.81.5, with 37 packages realigned. We removed a build plugin that had been forcing the Android Gradle Plugin back to an old version, audited every screen for edge-to-edge layout, and read the alignment of every library out of the finished bundle: 48 of 48 64-bit libraries at 16 KB. The same release moved the app to API 36.

Production received the new build first. The internal and alpha tracks were superseded with the same version the same afternoon, which cleared the target-API warning. Meanwhile, fixes that were pure JavaScript reached existing users as over-the-air updates against the version they already had installed, so customers didn't wait for the store build to get them.

A checklist for app owners

If your Android app was built more than a year ago, ask your developer to confirm each of these:

  • The app targets the API level Google Play currently requires
  • Every 64-bit native library in the release bundle is 16 KB aligned, checked in the bundle itself
  • No testing track still holds an old build targeting an old API
  • Screens have been checked edge to edge and on a large screen in both orientations
  • The framework version is recent enough for next year's requirement too

Questions people also ask

Does the 16 KB rule apply to my app?

If the app targets Android 15 or later and contains native code, yes. That includes React Native and Flutter apps, games built on engines and apps with native SDKs. Apps written only in Kotlin or Java without native libraries are usually unaffected.

Which React Native version supports 16 KB page sizes?

React Native 0.77 and later. For Expo apps, SDK 53 from version 53.0.14. Targeting Android 16 (API 36) as well needs Expo SDK 54, which ships React Native 0.81.

What target API level does Google Play require in 2026?

From 31 August 2026, new apps and updates must target Android 16 (API 36). Existing apps must target at least Android 15 (API 35) to remain available to new users on newer Android versions.

Can I delete an old build from a Google Play testing track?

No. Play Console cannot delete a release, a build or a track. Publish a newer version code to the track to supersede the old build.

Will users notice the upgrade?

Mostly not, but targeting a new Android version changes some behaviour: layouts extend behind the system bars, and on large screens the app may rotate. Test those before releasing.

More guides

Have an app to build or publish?

Tell us where it stands — idea, half-built or stuck in review — and we'll tell you the next step.

Talk to us
Contact Us

Let's Build Something Exceptional Together.

Whether you are looking to modernize operations, automate processes, or build a custom digital platform, UPGRADE is ready to partner with you.

Start your digital transformation today.

Location
Kuwait