Android release-readiness checks

Android release problems tend to be configuration problems. The difference between a debug and a release build is a handful of settings, and the ones that matter most are the cheapest in the world to check mechanically.

Detection

Run detection from the application module’s project directory. In a multi-module repository, the module you ship is the one to scan.

Terminal

guardian detect .

Release configuration

Area	Why it is read
Network security configuration	Whether the release build permits cleartext traffic beyond a documented exception.
Application manifest	What the application declares about itself, including the entry points it exposes to other applications.
Build configuration	Release build settings and how they differ from debug.
Dependency declarations	The inventory of what the application is built from.

What stays local

If you do analyse a built artefact, it stays where it is. Seesecurity and privacy for the full data-handling table.

Current limits

Exported-component checks, debuggable-build detection and minification configuration are documented as planned in thechecks catalogue. They are not published capabilities, and this page will not imply otherwise.
Transport configuration review is in preview, which means the direction is real and the exact coverage is not independently verified.
Guardian reads the project as written. Configuration assembled at build time is only visible if it exists when the scan runs.
Guardian does not sign, upload or submit anything to Google Play.