← Back to Updates & Guides

How to Fix "App Must Support 16 KB Memory Page Sizes" in Flutter & React Native (2026 Guide)

With Google Play enforcing Target API 36 (Android 16) and the mandatory 16 KB memory page size requirement ahead of the February 1, 2027 hard block, thousands of Flutter, React Native, and Unity developers are seeing release warnings on their .aab uploads.

⚡ Instant Browser Check (No CLI Needed)

Not sure which .so library inside your bundle is still compiled at 4 KB? Drop your .aab or .apk into our free browser scanner:

Open Android 16KB AAB Scanner →Flutter 16KB ScannerReact Native 16KB Scanner

1. Why Play Console Flags "4 KB LOAD Section Alignment"

Pure Java/Kotlin apps contain no native binaries and are automatically 16 KB compatible. Cross-platform apps built with Flutter, React Native, Expo, or Unity bundle compiled C/C++ shared libraries (lib/arm64-v8a/*.so). If even a single third-party plugin ships a binary with p_align = 0x1000 (4 KB), Play Console flags the entire release.

2. Fixing 16 KB Alignment in Flutter & Gradle (NDK r27)

Update your android/app/build.gradle to use Android NDK r27+ and modern JNI packaging:

android {
    ndkVersion "27.0.12077973"
    defaultConfig {
        externalNativeBuild {
            cmake {
                arguments "-DANDROID_SUPPORT_FLEXIBLE_PAGE_SIZES=ON"
                cFlags "-Wl,-z,max-page-size=16384"
                cppFlags "-Wl,-z,max-page-size=16384"
            }
        }
    }
    packagingOptions {
        jniLibs { useLegacyPackaging = false }
    }
}

3. Verify Your Bundle Before Submitting to Google Play

After rebuilding your release bundle, run it through the AABReady 16KB Page Size Checker and verify your SDK disclosures with the Google Play Data Safety Auto-Detector.