Reads AndroidManifest.xml and names every line that forces an extra Google Play Console declaration or an Android 14+ foreground-service permission, with the form Play will ask you to fill. Runs entirely in your browser — nothing is uploaded.
Same engine as the VS Code extension, byte for byte.
This page is the working piece. The full pack has everything below.
15 checks that name every Play Console declaration your manifest opens
A freelance Android release engineer bills $60-$120 an hour; reading a multi-module app's manifests against every current Play declaration is most of a working day
Buy the full version — $29It reads an AndroidManifest.xml and marks every line that Google Play treats as a declaration, not just a permission. The 15 checks cover app visibility, all files access, background location, SMS and call log, install unknown apps, photo and video, Health Connect, full-screen intent, exact alarms, the advertising ID, accessibility bindings, and the three foreground service rules.
Android developers and release engineers who upload to Google Play, and the person who reviews a manifest before a release branch is cut. It is most useful on manifests assembled by an assistant or merged in from an SDK, where a permission arrives without anyone deciding who will answer the Play Console form behind it.
Android Lint checks the manifest against the SDK, not against Play policy, so it stays quiet about declaration forms. A chatbot cannot see your file and will not know that your specialUse service is missing its subtype property. This runs on the file itself, offline, and prints a line number for each of the 15 checks.
The file open in your editor is free forever, with no key, no limit and no watermark: all 15 checks, marked in the Problems panel and listed in the output channel. The licensed part is scope and ownership - sweeping every manifest in the workspace, library modules included, into a dated playDecl-report.md you keep.
A freelance Android release engineer bills roughly $60-$120 an hour, and walking a multi-module app's manifests against every current Play declaration takes most of a working day. A single policy rejection costs more than the hours: the release waits for a re-review while the fix sits in a build queue.
One question, answered by the person who built it. Your email only if you want the answer sent.