Upload your APK or AAB. Get an instant report on every technical issue that could cause a Google Play rejection — debug build status, signing, SDK version, permissions, and more.
Eight automated checks covering every common technical cause of Google Play rejection.
Debug build detection
Instantly identifies if your APK or AAB was built in debug mode. Debug builds are rejected by Google Play before a human reviewer ever sees them.
Signing certificate
Verifies the signing certificate in your APK. Confirms whether you are using your release keystore or the debug keystore (which will cause rejection).
Target SDK version
Checks your targetSdkVersion against Google Play's current minimum requirement (API 35 as of 2026). Flags submissions that will be auto-rejected.
Permissions audit
Lists every permission declared in AndroidManifest.xml. Flags permissions commonly associated with policy violations or that typically require justification.
App metadata
Extracts app name, version code, version name, package name, and minimum SDK. Flags any values that look inconsistent or problematic.
ProGuard/R8 status
Checks whether code minification and obfuscation are enabled. Release builds should have minifyEnabled true.
Native library architecture
Confirms whether your native libraries include 64-bit variants. Required for new app submissions on Google Play.
Network security config
Checks for cleartext traffic permissions that may cause policy issues. Production apps should not allow unencrypted HTTP traffic.
Upload your APK or AAB
Drag and drop or select your Android app binary. Files are scanned in an isolated environment and not stored permanently.
Instant analysis
The analyzer extracts and inspects the manifest, certificates, and binary metadata. Results are returned in under 30 seconds.
Read your report
Each check is marked as pass, warning, or fail with a plain-English explanation and the specific fix for each issue found.
Fix and resubmit
Address any flagged issues, rebuild your release APK or AAB, and run the analyzer again to confirm before submitting to Google Play.
Most common rejection cause
A debug build submitted to Google Play is caught instantly by automated pre-screening. The APK analyzer catches this in seconds before you waste a review slot.
Review cycles cost time
A single Google Play review cycle takes between 1 hour and several days. A technical rejection means restarting the clock. The analyzer prevents this.
Signing errors are silent
Your app may appear to install and run correctly while being signed with the debug keystore. Only submission to Play Store reveals the issue — unless you check first.
SDK requirements change
Google's target SDK requirements are updated annually. The analyzer always checks against the current requirement, not the one from last year.
No account. No credit card. Upload your APK or AAB and get your report in under 30 seconds.
