Your web app is not the problem
HTML, CSS and JavaScript run inside Android System WebView, which Google ships and updates. Nothing in your Lovable, Bolt or Replit code is a native library.
What the requirement says, and when it applies
Android has traditionally used 4 KB memory pages. Starting with Android 15, devices can use 16 KB pages instead, which Google says improves performance. Native libraries that were linked for 4 KB pages can fail to load or crash on such a device, so Google Play requires that apps targeting Android 15 (API level 35) or higher support 16 KB page sizes on 64-bit devices.
The timeline moved more than once, which is why forum posts disagree:
- November 1, 2025: the requirement took effect for new apps and updates targeting Android 15 or higher.
- Until May 31, 2026: developers who needed more time could request an extension in Play Console.
- August 31, 2026: new apps and updates must target Android 16 (API level 36), so every new upload falls under the rule.
- February 1, 2027: Google's Android developer guide (updated in October 2026) states that from this date, updates that do not support 16 KB pages cannot be released.
The date and wording that Play Console shows for your own app are what count. Check them before you plan a release.
How Play Console tells you
The warning appears on the release pages and in the App bundle explorer, where Google shows whether a bundle supports 16 KB page sizes. Developers report wording along the lines of "Your app does not support 16 KB memory page sizes", sometimes followed by the path of the library that fails, such as base/lib/arm64-v8a/libexample.so. An existing app can also receive an Inbox message or email with the deadline that applies to it.
Before enforcement applies to your app it is a warning with a date. Once it applies, a non-compliant release cannot be rolled out, and the only way forward is a new bundle with aligned libraries.
Why a web-wrapped app is affected at all
The WebViewGold code is Java
Code written in Java or Kotlin does not depend on the page size. Google says apps without native code already support 16 KB devices.
SDKs can bring .so files
Scanning, ads, analytics, crash reporting, payment or media SDKs sometimes ship native libraries. If one of them is an old version, the whole bundle fails the check.
Old templates and toolchains
A template downloaded long ago, libraries copied into a jniLibs folder, or an Android Gradle plugin older than 8.5.1, which does not align uncompressed libraries on 16 KB boundaries.
Great work! Never coded anything but managed to work with this. Easy and fast! Also with great help from the creators!
Where the current WebViewGold template stands
WebViewGold lists full 16 KB memory page size support among its Android features, and the Android changelog includes improved 16 KB support in version 16.8 (May 2026). Building from the current template with the SDK versions it ships is the intended path to a compliant bundle. Two situations still deserve a check: a project you configured with an older version, and any library you added yourself.
The Cloud Builder always builds with the current template, so rebuilding an older app there without changing your settings is the quickest fix. In Android Studio, follow the template update steps in the target API level guide, which apply here unchanged. Because a rebuild for the current target level also switches on Android 15 edge-to-edge behavior, check the edge-to-edge guide in the same pass.
Check your bundle in about fifteen minutes
You need the signed build you want to release and Android Studio.
Look at the App bundle explorer
In Play Console, open App bundle explorer, pick the version and read the 16 KB compatibility information. If it reports the bundle as compliant, you are done with this topic.
Find out whether you ship native code
In Android Studio, build a signed release APK (Build menu, Generate Signed App Bundle or APK) and open it with Build, Analyze APK. If there is no lib folder or no .so files inside, the app has no native code and already supports 16 KB pages.
Check the alignment of each library
In APK Analyzer, the lib folder has an Alignment column that warns about files that are not 16 KB aligned. File names usually hint at the SDK that ships them.
Confirm with zipalign
Run the zipalign check from the Android SDK build tools on the APK, as shown below. The last line of the output should say "Verification successful".
Test on a 16 KB emulator
Create a virtual device with an Android 15 or newer system image labeled 16 KB Page Size, confirm the page size with adb, install the app and open the features that rely on SDKs, such as the scanner, ads or payments.
Fix, rebuild, upload
Update the template or the SDK that ships the unaligned library, rebuild with a higher version code and upload. The App bundle explorer shows the result for the new version.
Commands for the check
File names are examples. zipalign lives in the build-tools folder of your Android SDK, adb in platform-tools.
bash
# 1. Are all native libraries 16 KB aligned? (look for "Verification successful")
zipalign -v -c -P 16 4 app-release.apk
# 2. List the native libraries inside the APK
unzip -l app-release.apk | grep "\.so$"
# 3. Which dependency brings them in? (run in the project folder)
./gradlew app:dependencies --configuration releaseRuntimeClasspath
# 4. On the 16 KB emulator: should print 16384
adb shell getconf PAGE_SIZEFix by cause
| Cause | Fix |
|---|---|
| Project built with an older WebViewGold version | Download the current template (updates are free), carry over Config.java, icons and your manifest edits, rebuild. Or rebuild in the Cloud Builder. |
| An SDK you added ships an old .so file | Update the SDK to the version its vendor marks as 16 KB compatible, or remove it if you do not need it. |
| Your own C or C++ code | Build with NDK r28 or newer, which aligns to 16 KB by default. With older NDKs, add the linker flags -Wl,-z,max-page-size=16384 and -Wl,-z,common-page-size=16384. |
| Android Gradle plugin older than 8.5.1 | Update the plugin with the Android Studio upgrade assistant. Packaging libraries compressed (useLegacyPackaging) is only a last resort, because it increases the installed size. |
| A prebuilt .so with no update available | Replace the library or the feature that depends on it. No build setting turns a library linked for 4 KB pages into a compliant one. |
16 KB checklist
- App bundle explorer reports the bundle as 16 KB compatible.
- No alignment warnings for .so files in APK Analyzer, and the zipalign check passes.
- Built from the current WebViewGold template or in the Cloud Builder.
- Every SDK you added yourself is on a 16 KB-compatible version.
- Tested on a 16 KB emulator, including the features that use native SDKs.
- Version code increased before the upload.
Frequently asked questions
My app only shows my website. Do I need to do anything about 16 KB pages?
Check once. If the bundle contains no native libraries, it already supports 16 KB pages. If it contains .so files from SDKs, they must be aligned; the current WebViewGold template is built for that with the SDKs it ships.
Do I need to change my web app for the 16 KB requirement?
No. The requirement concerns native libraries in the Android bundle. HTML, CSS and JavaScript are not affected.
What happens to the version that is already live?
Existing installs keep working. The requirement controls which new releases you can publish. On a device with 16 KB pages, Android can run some unaligned apps in a compatibility mode that shows a warning, which is nothing to rely on.
Does the 16 KB rule matter for 32-bit libraries?
The Play requirement is about 64-bit devices, so the 64-bit libraries in your bundle (the arm64-v8a and x86_64 folders) are the ones that must be aligned. Keep the rest up to date anyway.
How do I find out which SDK ships the unaligned library?
The file name in the lib folder usually points to it, and the Gradle dependency tree shows which library pulls it in. If you cannot tell, send the file list together with your WebViewGold version to the support chat.
Three ways to get your app into the stores
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
Do it yourself
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main pageCloud Builder
$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demoFull Service
$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.