1. Google Play requires apps targeting Android 15 (API level 35) or higher to support 16 KB memory page sizes on 64-bit devices — this is a separate compatibility rule from the annual target API level bump (API 36 for new submissions as of August 31, 2026).
2. Apps written only in Java or Kotlin, including every library and SDK they ship, already comply. The rule applies when the artifact contains native code: NDK/C/C++, a third-party .so, or an app builder that packages native libraries on-device.
3. Rebuild native code with Android Gradle Plugin 8.5.1 or newer and NDK r28 or newer so every ELF LOAD segment is aligned to 2^14 (16 KB). An app can target API 36 and still fail this check if one prebuilt .so is 4 KB-aligned.
4. Before upload, open Android Studio APK Analyzer → lib/ and read the Alignment column. Any warning on a shared object means the bundle is not 16 KB-ready. Play Console also flags "App must support 16 KB memory page sizes" when PAGE_ALIGNMENT_16K fails.
5. Test on a 16 KB Android 15+ system image in the emulator. Libraries that only ever ran on 4 KB devices can fail to load or crash on 16 KB hardware even if the Play listing looks fine.
6. Third-party SDKs are the usual breakage: analytics, ads, payment, and game engines often ship old .so files. Confirm each vendor's 16 KB-compatible version and replace anything that has no rebuild.
7. Re-run APK Analyzer on every track (internal, closed, production). One leftover native dependency on a single track can block the whole update once Play enforces the 16 KB requirement on that artifact.