From February 1, 2027, Google Play won't let you release an update that doesn't support 16 KB memory pages. For Android TV and Wear OS apps it's already required: Play Console lists it from August 1, 2026 for TV and from September 15, 2026 for Wear OS. Only apps with native code are affected, and the fix depends on what the app is built with. Here are the versions each vendor says you need, and what to do when a third-party plug-in is the problem.
| Built with | What supports 16 KB pages |
|---|---|
| Unity | Unity 6000.1 and later, 6000.0.38f1+, 2022.3.56f1+, and 2021.3.48f1+ (2021.3 only under extended LTS for Enterprise and Industry customers). Burst package 1.8.21 or later. |
| React Native / Expo | React Native 0.77 and later. With Expo, that means SDK 53; Expo recommends expo@53.0.14 or newer. |
| .NET MAUI / .NET for Android | .NET 9 and later, out of the box. Use .NET 10 or later: .NET 9 reached end of support on November 10, 2026. NuGet packages that bring in native libraries (SkiaSharp, for example) need versions with 16 KB-aligned binaries too. |
| Xamarin | No fix is coming: Xamarin support ended on May 1, 2024. Xamarin.Android apps move to .NET for Android, and Xamarin.Forms apps to .NET MAUI. |
| Flutter | The sources we checked give no single minimum Flutter version. Use the current stable Flutter with AGP 8.5.1+ and NDK r28+, update plug-ins that contain native code, then rebuild and check. |
| Your own C/C++ code (NDK) | NDK r28 and later build 16 KB-aligned libraries by default. NDK r27 and older need two linker flags (below). |
| Cordova, Capacitor, Ionic | The WebView part has no native code. Native libraries come from plug-ins (SQLite, barcode scanning, crypto and the like), so those plug-ins need updating. |
.so plug-in is not 16 KB-aligned. Ask the plug-in's author for a 16 KB build or replace the plug-in..so files); moving to a new .NET doesn't fix an old package's binaries. For SkiaSharp, libSkiaSharp.so comes in the SkiaSharp.NativeAssets.Android package, which SkiaSharp pulls in; SkiaSharp.Views.Maui.Controls has no .so of its own. SkiaSharp's release notes put the 16 KB alignment update in 3.116.1, so move SkiaSharp and SkiaSharp.Views.Maui.Controls, and any direct reference to SkiaSharp.NativeAssets.Android, to 3.116.1 or later.-Wl,-z,max-page-size=16384 and -Wl,-z,common-page-size=16384, to LOCAL_LDFLAGS in Android.mk for ndk-build or to target_link_options in CMakeLists.txt for CMake. Google's guide warns that a library built with these NDKs without the flags can crash with a segmentation fault (SIGSEGV) on 16 KB devices: if its RELRO segment doesn't end on a 16 KB boundary, writable data on the same page becomes read-only. NDK r27's flexible page size option (ANDROID_SUPPORT_FLEXIBLE_PAGE_SIZES, APP_SUPPORT_FLEXIBLE_PAGE_SIZES) adds only max-page-size, so add common-page-size even if you turned it on, or move to NDK r28 or later..so files from SDK vendors can't be fixed by your flags: get a 16 KB-ready version from the vendor.zipalign -c -P 16 checks.useLegacyPackaging set to true), zip alignment doesn't apply, and zipalign -c -P 16 reports them as OK even when the libraries themselves are built with 4 KB alignment. The ELF alignment inside each library still has to be 16 KB. Our checker reads it and flags those libraries.arm64-v8a and x86_64) are checked against the 16 KB rule.adb shell getconf PAGE_SIZE should print 16384.