Check app
How to check an APK or app bundle before Google Play does
Check app reads your APK or .aab inside your browser — the file is never uploaded, and the check works with the network off — and lists what Google Play will object to: what will block a release, what's worth fixing and what's good to know. Each finding says why Play cares, shows the evidence, links Google's own page, and gives the lines to paste where the fix is code.
Try it live, with the sample app
The report on Publishly's sample APK, a tiny app built to carry the mistakes the checks look for. It loads the real tool right here, with a made-up app. Nothing you do in it is saved, and your own work isn't touched.
Step by step
Bring your build
Drop the
.apkor.aabon the page, or Choose an APK or AAB (up to 600 MB). A build another tool already opened is one click away: Use, followed by its name. No build to hand? See it on a sample app.Read the summary
The app's package, version and target API come first, then the findings in three groups — Will block a release, Worth fixing and Good to know — and a line counting the requests that left the page while it was read: none.
Work through the findings
Filter by Google Play rules, Permissions, Security, Device compatibility, Libraries or Reach. Open a finding for What to do, the evidence from your build, code to paste with a Copy button, and Google's page on this.
Check the libraries and Data safety
What this app is built with lists the SDKs found; Check for newer versions looks them up on Google's Maven (it sends only their names). Under Data safety, as a starting point, drop the CSV Play Console exports: the data types get ticked in it, ready for Import from CSV.
Sort out the privacy policy
Paste your policy's address and Check it. No policy yet? Draft one from this APK asks who publishes the app and a contact email, then Write the draft — copy it, or save it as Markdown or a web page. Gaps are marked
[to confirm].Compare and keep it
What changed since your last release: Choose the other build to see new permissions, a lower target SDK or dropped languages. Take it with you: Download as Markdown. The report on your own app is kept in this browser for the release checklist.
What it looks for
- Play deadlines: target SDK, 16 KB page alignment for native libraries, 32-bit-only builds — each with its date.
- Permissions: the risky ones, the narrower API to use instead, and whether Play Console needs a declaration.
- Security: debuggable builds, cleartext traffic, exported components, backup rules, and keys left in the code.
- Signing: debug certificates, v1-only signatures and certificate expiry.
- Crash readiness: whether the mapping file and native debug symbols Play needs are there.
- Libraries: about 30 SDKs recognised, with Data safety hints for each.
No AI, no upload
The checks are rules read from the build — no AI is involved. Only Check for newer versions and Check it (which fetches your policy page) use the network. Every check is listed on the Play checks page.
From the command line
The same checks run in a terminal or CI: npx @publishly/cli check app-release.aab, with --out for Markdown and --sarif for findings on pull requests.
Questions
Is my APK uploaded?
No. It's read in your browser, and the page counts its own requests to show it. Only the library lookup sends anything — the libraries' names, never the build.
Does it work with app bundles (.aab)?
Yes. App bundles are read the same way, manifest and resources included.
Is every Play policy covered?
No tool can promise that. The checks cover what a build can show; questions that depend on your app's content and behaviour are still yours to answer.
Other guides
Last checked against the app on 2026-10-20.