Play Store flagged your app for 16 KB memory page sizes?We rebuild + re-submit in 1–3 days.

Android 15 (API 35+) introduced support for 16 KB memory page sizes on new device hardware, a performance improvement on top of the long-standing 4 KB page size. Apps that ship native (NDK) libraries built only for 4 KB pages will not load correctly on 16 KB devices. Google Play has therefore made 16 KB support a publishing requirement: from 1 February 2027, apps targeting Android 15+ that do not support 16 KB pages can no longer publish new releases.

Very. The “Action by 1 February 2027” banner means Google has given you a fixed grace window. After that date Google blocks all new releases for your app (including hot-fixes, security patches and seasonal updates) until you ship a 16 KB-supporting build. Your existing release stays live on Play, but you cannot push updates. We recommend fixing this at least 2–3 weeks before the deadline.

Two reasons. (1) To confirm the actual blocking warning on your listing: Play Console is the only source of truth, and the policy can look different per app and per track. (2) To upload the rebuilt AAB on your behalf, so the new release publishes under your existing listing, with your existing keystore, with no impact on your installed users. We send you a one-page guide on how to add us with the minimum roles needed.

Because we have to do recovery work first. With source code, we just bump the NDK and Gradle, rebuild and re-test, usually in 1–3 working days. Without source code, we pull the latest AAB from Play Console, decompile it, identify the 4 KB-aligned native libraries, upgrade the toolchain and rebuild. That recovery and verification work adds days and risk, so the fee is quoted per case. We always quote you the lower price first if it applies.

No. As long as we re-sign with your existing keystore (the same .jks/.keystore, key alias and passwords) and ship under the same Package ID, your existing users are upgraded in place: same login, same orders, same preferences, same push token. Google Play will not let us change the keystore or the Package ID for an existing app even if we wanted to.

A lost keystore is the one problem we may not be able to work around. If your app uses Play App Signing, Google keeps the app signing key, and a lost upload key can be reset from Play Console; we will guide you through it. If you signed the app yourself without Play App Signing, Google Play only accepts updates signed with the original key, so the only option is a new listing with a new Package ID, which we can scope as a separate job.

No. Any Android app shipping native libraries needs the 16 KB fix: Flutter, Kotlin native, Java native, React Native, Cordova and Ionic, Unity, custom in-house apps. CodeCanyon scripts (6amMart, StackFood, 6Valley, eFood, Demandium, DriveMond, HexaCom, GroFresh) are the most common case we see, because they bundle multiple SDKs that need the rebuild.

1–3 working days when you have the source code and keystore, and our access to Play Console is approved. 3–7 working days when we have to recover from the published AAB. The clock pauses if we are waiting on access from your side. You will see the live timer on the project page.

No. This service covers Android and the Play Store only. iOS goes through Apple's own review (App Review, privacy manifests), which we handle separately. If you also need an iOS update, say so in the same enquiry and we will quote both.

New apps that already target Android 15+ must support 16 KB pages from the start. That is part of our normal Google Play app submission service. This page is for existing apps that were built before 16 KB became a publishing requirement.