Google Play says the app does not support 16 KB memory pages
Play Console warning that app updates must support 16 KB memory page sizesShort answer
Google Play requires apps that target Android 15 or higher and ship native .so libraries to run on devices with 16 KB memory pages; from 1 February 2027 it will block updates that do not. A Flutter app passes when the engine, every plugin library and the packaging are 16 KB aligned: Flutter 3.38 or later, NDK r28 or later, AGP 8.5.1 or later, and current plugins.
Fix it fast
1Find out which cause you have
Build a release APK and run zipalign's 16 KB check on it. Android's guide asks for zipalign from build-tools 35.0.0 or newer for this check. The filter keeps the native library lines and the verdict; 'Verification successful' means every library is aligned, and any library line not marked OK is the one to chase.
flutter build apk --release "$ANDROID_HOME/build-tools/36.0.0/zipalign" -c -P 16 -v 4 build/app/outputs/flutter-apk/app-release.apk | grep -E "lib/|Verification"2Match what you see, then jump to its fix
- 1
flutter --version shows a release before 3.38, or ndkVersion is missing or pinned below 28The Flutter SDK is older than 3.38Fix - 2
The failing library has a vendor name (an ads, analytics, video, database or ML SDK), and its LOAD lines show align 2**12 or 2**13A plugin or third-party SDK ships a prebuilt .so built for 4 KB pagesFix - 3
bundletool prints PAGE_ALIGNMENT_4K, or the APK built locally works but the one Play builds from the bundle will not install on 16 KB devicesThe libraries are fine but the bundle packs them with 4 KB zip alignmentFix - 4
SIGSEGV in your own or a vendor's native library, only on 16 KB devices or emulatorsNative code built with NDK r27 or older crashes even though it is alignedFix - 5
Aligned build, but crashes or memory errors appear only on 16 KB devices, often in custom C or C++ reached through dart:ffiCode assumes every memory page is 4096 bytesFix
- 1
What does the error look like?
Play Console warning that app updates must support 16 KB memory page sizescheck_elf_alignment.sh reports UNALIGNED for a library under lib/arm64-v8aLOAD off … align 2**12 (llvm-objdump on a .so file)PAGE_ALIGNMENT_4K (bundletool dump config)A warning on first launch on a 16 KB device that the app is running in 16 KB backcompat mode
Cause 1 of 5
The Flutter SDK is older than 3.38
1Check
Google's date, checked on Android's page-size guide on 16 November 2026: every app targeting Android 15 or higher must support 16 KB pages on 64-bit devices, and updates that do not will be blocked from 1 February 2027. Play's quality page lists earlier dates for Android TV (1 August 2026) and Wear OS (15 September 2026). Flutter 3.38 moved its default NDK to r28, the first NDK that aligns native code for 16 KB pages by default; current stable uses 28.2.13676358.
flutter --version
grep -n "ndkVersion" android/app/build.gradle*2Fix
Upgrade Flutter and let the app module take the NDK version from Flutter, so the next upgrade moves it too.
flutter upgrade
// android/app/build.gradle.kts
android {
ndkVersion = flutter.ndkVersion
}3Verify
Rebuild and run the zipalign check again; the Flutter libraries no longer appear as failures.
flutter clean && flutter build apk --releaseCause 2 of 5
A plugin or third-party SDK ships a prebuilt .so built for 4 KB pages
1Check
Plugins often wrap native SDKs that arrive already compiled, so upgrading your own NDK changes nothing for them. Unpack the APK and read the LOAD segment alignment of each library; 2**14 means 16 KB, anything smaller fails.
unzip -o -q build/app/outputs/flutter-apk/app-release.apk 'lib/*' -d /tmp/apk_libs
OBJDUMP="$ANDROID_HOME/ndk/28.2.13676358/toolchains/llvm/prebuilt/darwin-x86_64/bin/llvm-objdump"
for f in /tmp/apk_libs/lib/arm64-v8a/*.so; do echo "$f"; "$OBJDUMP" -p "$f" | grep LOAD; done2Fix
Find which package brings that library in and upgrade it; many SDK vendors publish 16 KB compatible builds and say in their release notes which version that is. If a plugin has no fixed release, replace it or ask the maintainer to update the bundled SDK. Plugins you maintain that build C or C++ with CMake need NDK r28, or the linker flags below on r27 and older.
flutter pub outdated
flutter pub upgrade some_plugin
# CMakeLists.txt of your own FFI plugin, only on NDK r27 or older
target_link_options(${PROJECT_NAME} PRIVATE
"-Wl,-z,max-page-size=16384"
"-Wl,-z,common-page-size=16384")3Verify
Every library in lib/arm64-v8a and lib/x86_64 now shows align 2**14.
for f in /tmp/apk_libs/lib/x86_64/*.so; do "$OBJDUMP" -p "$f" | grep LOAD; doneCause 3 of 5
The libraries are fine but the bundle packs them with 4 KB zip alignment
1Check
Uncompressed .so files must also sit on 16 KB boundaries inside the zip. Android documents that AGP 8.5.1 is the first version that does this for bundles; on 8.3 to 8.5 a locally built APK can look fine while the APKs Play generates from the bundle are not.
flutter build appbundle --release
java -jar bundletool.jar dump config --bundle=build/app/outputs/bundle/release/*.aab | grep alignment
grep -n "com.android.application" android/settings.gradle*2Fix
Raise AGP to 8.5.1 or later in settings.gradle(.kts), with the Gradle version Android's table requires. If an old AGP has to stay for now, Android's fallback is to compress native libraries, at the cost of larger installs.
// android/app/build.gradle.kts, only while stuck on AGP below 8.5.1
android {
packagingOptions {
jniLibs {
useLegacyPackaging = true
}
}
}3Verify
bundletool now reports PAGE_ALIGNMENT_16K for the new bundle.
java -jar bundletool.jar dump config --bundle=build/app/outputs/bundle/release/*.aab | grep alignmentCause 4 of 5
Native code built with NDK r27 or older crashes even though it is aligned
1Check
The read-only relocation segment (GNU_RELRO) must end on a 16 KB boundary when writable data follows it in the same LOAD segment. Libraries linked with NDK r27 or older without the 16 KB flags can pass the alignment check and still crash on first write. Print the program headers and compare the end of GNU_RELRO with its LOAD segment.
READELF="$ANDROID_HOME/ndk/28.2.13676358/toolchains/llvm/prebuilt/darwin-x86_64/bin/llvm-readelf"
"$READELF" -Wl /tmp/apk_libs/lib/arm64-v8a/libsomething.so | grep 'LOAD\|RELRO\|Type'2Fix
Rebuild the library with NDK r28 or newer, or with the 16 KB linker flags on older NDKs. For a vendor library, the only fix is the vendor's updated build.
# ndk-build projects, NDK r27 or older
LOCAL_LDFLAGS += -Wl,-z,max-page-size=16384 -Wl,-z,common-page-size=163843Verify
Run the app on a 16 KB emulator image and confirm the page size first.
adb shell getconf PAGE_SIZE # expect 16384
flutter run --releaseCause 5 of 5
Code assumes every memory page is 4096 bytes
1Check
Native code that hard-codes 4096, or relies on the PAGE_SIZE constant for mmap sizes and offsets, breaks when pages are four times larger. NDK r27 and newer leave PAGE_SIZE undefined in 16 KB mode for that reason.
grep -rn "4096\|PAGE_SIZE" android/ ios/ src/ native/ 2>/dev/null | grep -v build/2Fix
Ask the system for the page size at runtime and size buffers and mappings from that value.
#include <unistd.h>
long page = sysconf(_SC_PAGESIZE); // 4096 or 163843Verify
Run the native code paths on the 16 KB emulator image (Google APIs Experimental 16 KB Page Size system image in the SDK Manager).
adb shell getconf PAGE_SIZEHow do I stop it coming back?
- Add the zipalign -P 16 check to CI on every release build, so a plugin update that brings back a 4 KB library fails the pipeline.
- Keep ndkVersion on flutter.ndkVersion and upgrade Flutter on a schedule rather than at the deadline.
- Before adding a plugin with native code, check its changelog for 16 KB support and run the alignment check on a test build.
- Keep a 16 KB emulator image in your device list and run a smoke test on it before each release.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
Related fixes
Mobile apps
Play Console will not accept the release because of its target API level
A target API level warning on the Policy status page, with an extension form link
Since 31 August 2026, Google Play accepts new phone and tablet apps and updates only if they target Android 16 (API level 36); the extension window ran to 1 November 2026.
5 causes, each with a fixMobile apps
Flutter Android build stops with Execution failed for task ':app:…'
Execution failed for task ':app:compileFlutterBuildRelease'.
The line only tells you which Gradle step broke; the task name in the quotes tells you why.
5 causes, each with a fixMobile apps
Gradle cannot find com.google.firebase:firebase-analytics-ktx
Required by: project :app
Firebase moved the Kotlin extensions into the main modules and stopped releasing the -ktx modules in July 2025.
2 causes, each with a fixMobile apps
Gradle cannot create LibraryVariantBuilderImpl in a Flutter Android build
Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl
This error appears when the Android Gradle plugin (AGP) cannot run in the Gradle or IDE you use.
3 causes, each with a fixMobile apps
Flutter release build cannot open the keystore: HmacPBESHA256 not available
Algorithm HmacPBESHA256 not available
The keystore is a PKCS12 file protected by a newer algorithm than the Java that is reading it understands.
3 causes, each with a fixMobile apps
Android install error: the package conflicts with an existing package of the same name
The package conflicts with an existing package by the same name
Android allows only one app per application ID, and an update must be signed with the same certificate as the installed version.
3 causes, each with a fix