Learn
Documentation
Everything you need to run a scan, read the report, and fix issues—written in plain language.
Full Play Console guide
Fix the 16 KB rejection
What “Not compatible with 16 KB page size devices” means, how to detect it, fix it, and verify before re-uploading.
Read guideTechnical walkthrough
How the scan works
Where results live in your browser, exports, file limits, and Strict vs Studio-style.
Read guideFramework guide
Flutter 16 KB fix
Upgrade Flutter, pin the NDK, audit plugins, and verify the AAB before Play Console rejects it.
Read guideFramework guide
Unity 16 KB fix
Which Unity LTS versions emit 16 KB-aligned engines, IL2CPP settings, and how to audit Asset Store plugins.
Read guideWhat we check
Four pillars of every scan—each section in your report maps back to one of these.
16 KB native rule
On 64-bit libraries we read alignment in the file and compare it to Google’s 16 KB bar (shown as p_align vs 0x4000).
Manifest (app details)
App name, lowest and target Android versions, permissions with simple risk tags, and exported screens or services.
Size chart
Code, native libraries, images/resources, and other parts as a share of the whole download.
Framework hints
Best-effort guesses (Flutter, Unity, ads SDKs, and more) from paths inside your package.