You've spent weeks or months building your Android application. Your features work, your interface looks good, and you're ready to publish.
But is your app actually ready for Google Play?
A successful build doesn't automatically mean a successful submission. Problems involving Android App Bundles, permissions, privacy declarations, testing, and Play Console requirements can still delay your release.
Here are seven important checks worth completing before uploading your .aab file.
- Validate Your Android App Bundle
Before submission, confirm that your release AAB is properly generated and contains the expected application configuration.
Check your application ID, version code, signing configuration, and release build settings.
Google's bundletool can help validate an Android App Bundle. Avoid relying exclusively on a successful Gradle build.
- Check Your Target SDK Requirements
Google Play updates its target API level requirements over time.
Confirm that your application's target SDK meets the current requirements for your submission type.
Always consult the latest official Google Play documentation rather than relying on an older development tutorial.
- Review Permissions Carefully
Does your application request permissions it doesn't actually need?
Review permissions declared in your manifest, including those added through third-party libraries.
Sensitive permissions may require additional Play Console declarations or policy justification.
The goal is to request only what your application genuinely needs.
- Verify Your Privacy Policy and Data Safety Information
Your Play Console Data safety declarations should accurately reflect your application's behavior, including relevant third-party SDKs.
Check what information your application collects, shares, and processes.
If your application supports account creation, review Google's applicable account-deletion requirements.
A privacy policy URL alone does not prove that your declarations are accurate.
- Test Real Application Behavior
Don't assume an app is ready just because it works on your personal phone.
Test installation, first launch, login, navigation, network failures, and critical application features.
Consider different Android versions, screen sizes, and device configurations.
Use Google Play's available testing and pre-launch tools where applicable.
Static AAB checks cannot replace actual device testing.
- Review Your Play Store Listing
Check your application name, descriptions, icon, screenshots, feature graphic, category, and required declarations.
Your listing should accurately represent what users will experience.
Avoid misleading claims or screenshots showing functionality that isn't available in the submitted release.
- Perform a Final Pre-Submission Review
Before pressing Submit, review the exact release bundle you're planning to upload.
Use a checklist to catch issues early, confirm that your Play Console declarations are complete, and document any findings that still need attention.
This is also the problem that led me to build PreStrikeCheck.
PreStrikeCheck is an Android pre-submission checking tool designed to help developers identify potential issues in their Android App Bundles before submitting to Google Play.
It is an additional preparation tool, not a guarantee of Google Play approval or a replacement for device testing and Play Console review.
You can learn more at:
Visit PreStrikeCheck — Check Before You Submit
Final Thoughts
Google Play publishing can be frustrating, particularly when a preventable issue delays a release.
A few extra checks before submission can save unnecessary troubleshooting later.
Check Before You Submit.
What's the most frustrating issue you've encountered when publishing an Android application to Google Play?
I'd be interested to hear other developers' experiences.
