You drop your signed Android App Bundle (.aab) into Step 1 — Create release in Google Play Console without a single red error, click Next, and get stopped on Step 2 — Preview and confirm by this card:
Recompile your app with 16 KB native library alignment
Your app uses native libraries that are not aligned to support devices with 16 KB memory page sizes. These devices may not be able to install or start your app, or the app may start and then crash.
Underneath, Play Console adds There are new app bundles in this release that do not support 16 KB.—and in App bundle explorer or Policy status, the same issue shows up as App must support 16 KB memory page sizes or Does not support 16 KB.
This catches developers off guard because you don't need to write a single line of C or C++ to trigger it. When your app targets Android 15 (API level 35) or higher, Google Play checks every 64-bit native .so file inside your .aab. Cross-platform runtimes (libflutter.so, libil2cpp.so, libreactnative.so, libhermes.so) and everyday plugins for cameras, barcode scanning, local databases, or machine learning all bundle precompiled .so libraries that used to be built with 4 KB ELF alignment instead of 16 KB.
1Find which .so files are actually failing
Before upgrading everything at random, check whether the unaligned .so files come from your framework engine, your Gradle packaging, or one specific third-party SDK:
- On the release screen (
Preview and confirm): Click to expandLibraries that do not support 16 KB:directly under the message. Play Console lists the exact.sopaths inside your bundle—for example,base/lib/arm64-v8a/libflutter.so(your framework runtime) versusbase/lib/arm64-v8a/libbarhopper_v3.so(a barcode-scanning SDK). - In App bundle explorer: Go to Test and release > Latest releases and bundles, open the uploaded
versionCodein App bundle explorer, and check the memory page size field (Does not support 16 KB) on the Details tab. - Locally before burning another
versionCode(optional): In Android Studio, open Build > Analyze APK… and select your.aabor.apk. Check the Alignment column underlib/arm64-v8a/—any.sostill aligned to4 KBis flagged immediately so you can verify your fix before uploading again.
2Fix by framework
Two parts of your Android build must agree: Android Gradle Plugin (AGP) 8.5.1+ zip-aligns uncompressed .so entries on 16 KB boundaries inside the bundle, and your compiler/engine must build those .so binaries with 16 KB ELF segment alignment.
Android Studio / Native Gradle
Upgrade AGP to 8.5.1+ and Android NDK to r28+ (28.0.13004108 or newer), which enables 16 KB ELF alignment by default:
// Root build.gradle.kts (or set agp = "8.7.3" in gradle/libs.versions.toml)
plugins {
id("com.android.application") version "8.7.3" apply false // 8.5.1 or higher
}
// app/build.gradle.kts
android {
ndkVersion = "28.0.13004108" // NDK r28+ compiles with 16 KB alignment by default
}
If you cannot move off NDK r27 yet, pass the 16 KB page-size flag explicitly (-Wl,-z,max-page-size=16384 for linker flags, or -DANDROID_SUPPORT_FLEXIBLE_PAGE_SIZES=ON in CMake):
android {
defaultConfig {
externalNativeBuild {
cmake {
arguments += listOf("-DANDROID_SUPPORT_FLEXIBLE_PAGE_SIZES=ON")
}
}
}
}
Also check packaging { jniLibs { useLegacyPackaging } } in build.gradle(.kts): leave it unset (default false) on AGP 8.5.1+ so uncompressed .so libraries are 16 KB zip-aligned automatically.
Flutter
Running flutter upgrade updates the Flutter engine (libflutter.so), but older projects keep their existing Gradle and NDK versions in android/ until you edit them:
- Upgrade to Flutter
3.27+or3.29+(flutter upgrade). - In
android/settings.gradle(orsettings.gradle.kts), bumpcom.android.application(AGP) to8.5.1+(and make suregradle-wrapper.propertiesuses Gradle8.7+, such as8.9). - In
android/app/build.gradle(orbuild.gradle.kts), pin NDKr28+:
android {
ndkVersion = "28.0.13004108"
}
- Run
flutter pub upgradeso plugins carrying native.socode pull their 16 KB-compiled versions, increment+versionCodeinpubspec.yaml, and rebuild cleanly withflutter cleanfollowed byflutter build appbundle --release.
Expo / React Native
React Native added official 16 KB page size support for libreactnative.so and libhermes.so in React Native 0.77:
- Expo: Upgrade to Expo SDK
52+or53+(SDK53+includes React Native0.79with full 16 KB support out of the box), runnpx expo install --fixso every native Expo module matches your SDK, bumpandroid.versionCodeinapp.json, and runeas build --platform android --profile production. - Bare React Native: Upgrade to React Native
0.77+, verifyandroid/build.gradleuses AGP8.5.1+andndkVersion = "28.0.13004108", and run a clean release bundle build.
Unity
In Unity projects, libil2cpp.so and libunity.so come directly from the Unity Editor installation—changing Gradle templates alone will not re-align an older editor's engine libraries. Upgrade your project to a 16 KB-patched editor release:
- Unity 6:
6000.0.38f1or newer - Unity 2022 LTS:
2022.3.56f1or newer - Unity 2021 LTS:
2021.3.48f1or newer (Enterprise / Industry Extended LTS only; Personal users should upgrade to Unity 2022 LTS or Unity 6)
Then open Project Settings > Player > Android > Other Settings, confirm Scripting Backend is set to IL2CPP with ARM64 checked, increment Bundle Version Code, and export with Build App Bundle (Google Play) enabled.
3What if a third-party SDK's .so still fails?
NDK r28+ only compiles C/C++ code built from source during your Gradle build. Most Maven, pub.dev, npm, and Unity .aar packages ship precompiled .so binaries built by the vendor. If Libraries that do not support 16 KB: still flags a library such as libbarhopper_v3.so, libmmkv.so, or libsqlcipher.so after upgrading your toolchain:
- Trace which dependency packed the
.so: Searchbuild/intermediates/merged_native_libs/release/for the.sofile name, or run./gradlew :app:dependencies --configuration releaseRuntimeClasspathto see which package pulled it in. - Check for major-version SDK upgrades: Common libraries—including ML Kit Barcode Scanning (
17.3.0+), CameraX (1.4.0+), MMKV (1.3.9+/2.0+), Realm, and SQLCipher—ship 16 KB binaries in newer major versions that a conservative^constraint inpubspec.yamlorpackage.jsonwon't pick up automatically. - Remove unused native plugins: Starter templates often leave behind PDF viewers, image compressors, or scanner packages your app no longer imports. Removing an unused dependency drops its
.sofrom the bundle immediately. - When a vendor still hasn't shipped a 16 KB binary: If the library is open-source, compile it from source with NDK
r28+; if it is abandoned (for instance,android-database-sqlcipher), migrate to its maintained replacement (sqlcipher-android). Avoid binary-patching precompiled 4 KB.sofiles withpatchelforobjcopy—altering ELF headers without recompiling breaks internal page-offset assumptions and causes crashes on real 16 KB devices.
4Why the error sometimes stays after uploading a fixed .aab
If Android Studio's Analyze APK… confirms every .so in your new .aab is 16 KB-aligned, yet Play Console still warns or blocks you, check two release-management traps:
- The old 4 KB bundle is still attached to your draft release: Uploading a new
versionCodeinto an existing draft does not always remove an earlier failed bundle sitting in the same draft. Check App bundles on the Create release screen and remove any olderversionCodeso only the newly aligned.aabremains. - An older 4 KB bundle is still active on another track: Policy status (
App must support 16 KB memory page sizes) checks every active bundle across all tracks—including Internal testing, Closed testing, and Open testing. Even after Closed testing has a clean 16 KB build, an older 4 KB build left active on Internal testing keeps your app flagged. Promote your new bundle to that track via Add from library to supersede the old build, or click Pause track on unused test tracks.
Passed Preview and confirm? What comes next
If clearing 16 KB alignment reveals another Play Console check right behind it—such as an AD_ID permission mismatch, a duplicate versionCode, or yellow warnings about R8 deobfuscation and debug symbols—look up the exact message in Google Play Console AAB Upload Errors: Causes and Fixes.
Once your closed testing release rolls out on a personal developer account, the next hurdle is Google's mandatory testing gate: you must run your closed test with at least 12 testers for 14 days continuously before you can apply for access to production (see 12 Testers for 14 Days: What "Continuously" Really Means).
If you still need those 12 testers—and want your newly aligned build running on real physical Android phones rather than sitting idle after opt-in—BetaLobby (free, no paid plans) groups 16 developers into one Team mode squad for the 14-day run, verifies real device installs automatically, and logs daily check-in opens from day 1 to day 14.