Skip to content

Google Play requirementGoogle Play: app doesn’t support 16 KB memory page sizes

16 KB page size support is a Google Play requirement for apps targeting Android 15 (API level 35) and higher on 64-bit devices. Apps with native code, such as Flutter, React Native and game engine apps, need native libraries built and packaged for 16 KB pages.

Short answer

Find the .so files that fail in the Play Console warning or the APK Analyzer. Upgrade the Android Gradle Plugin to 8.5.1 or higher, build your own native code with NDK r28 or newer, and update SDKs that ship native libraries. Check an APK with zipalign and the bundle with bundletool before you upload.

Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.

Why the app fails the 16 KB check, and the fix

  1. 01

    The Android Gradle Plugin is too old

    “To do this, you need to upgrade to Android Gradle Plugin (AGP) version 8.5.1 or higher.” Android Developers, Support 16 KB page sizes

    Uncompressed native libraries must sit on a 16 KB boundary in the APK. Older plugin versions can build an app that runs locally but won’t install when Play builds it from the bundle.

  2. 02

    Your native code uses an old NDK

    “NDK version r28 and higher compile 16 KB-aligned by default.” Android Developers, Support 16 KB page sizes

    C or C++ code built with NDK r27 or lower needs extra linker flags. Upgrading to r28 or newer is simpler.

    # NDK r27 or lower: add these linker flags
    -Wl,-z,max-page-size=16384
    -Wl,-z,common-page-size=16384
  3. 03

    An SDK ships old native libraries

    Ads, analytics, maps, video and game SDKs often include .so files. Update each one to a version built for 16 KB pages, and update Flutter or React Native and their native plugins too. If a vendor has no update, replace that SDK.

  4. 04

    You aren’t sure the app has native code

    “If your app only uses code written in the Java programming language or in Kotlin, including all libraries or SDKs, then your app already supports 16 KB devices.” Android Developers, Support 16 KB page sizes

    Open the APK in the APK Analyzer and look for a lib folder. If it has .so files, check zip alignment with zipalign (build-tools 35 or newer); the last line should say Verification successful. For the bundle, bundletool dump config should show PAGE_ALIGNMENT_16K.

    zipalign -v -c -P 16 4 app-release.apk

Checked against the vendor’s docs on : Android Developers: Support 16 KB page sizes.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
A buyer in the United States, July 2022. Shopify on Fiverr
All 127 Fiverr reviews

Related: Google Play target API level 35 · Google Play native code debug symbols · Flutter Kotlin Gradle plugin version · Google Play QUERY_ALL_PACKAGES

Questions

More on this launch

When does Google Play block releases?

Android’s guide says that from February 1, 2027, app updates that don’t support 16 KB page sizes can’t be released. Fix it before then so your next update can ship.

Does a Flutter or React Native app need changes?

Usually an upgrade. Both ship native libraries, so move to a version built for 16 KB pages, update plugins with native code, and test on a 16 KB emulator.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

Something else?

Describe it and get a written quote

Describe the app and where it is in the launch. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.