Drop your APK or AAB below. This page checks the two rules that block updates: 16 KB memory page support in native libraries (required from February 1, 2027) and target API 36 (required since August 31, 2026). The file is read in your browser and never uploaded.
You don't need a developer to get one. In Google Play Console, go to Test and release → Latest releases and app bundles, choose the latest version, open the Downloads tab and download the Signed, universal APK. Apps on Play App Signing have it for every release.
arm64-v8a, x86_64): every LOAD segment aligned to at least 16 KB, the GNU_RELRO rule (no writable data may share a 16 KB page with the end of RELRO), and, in an APK, 16 KB zip alignment of uncompressed libraries. In an AAB it also reads the bundle's page alignment setting. These are the rules on Google's 16 KB page sizes page.It only reads library headers and the manifest. It can't see runtime problems, such as code that assumes 4 KB pages; test on a 16 KB emulator before you ship.
No. JavaScript in this page reads the file on your computer. You can check the Network tab of your browser's developer tools: the only requests are the page itself and the security check that our host, Cloudflare, runs when the page loads. Your file is never sent.
Libraries that fail usually need a newer version of the SDK that ships them, or a rebuild with NDK r28 or later and Android Gradle Plugin 8.5.1 or later. If nobody on your team can do it, we update old apps at a fixed price: start with the $290 store-compliance check.
Xamarin stopped at API 34, so a Xamarin app can't meet the API 36 rule, and Google Play won't accept its updates. The way forward is .NET MAUI: see our Xamarin to .NET MAUI 11 migration.
No. It's a free tool by BestPaid, not affiliated with Google. For an official answer, use the APK Analyzer in Android Studio or zipalign -c -P 16 -v 4.