Building and Publishing
Android Release Checklist
Move a tested Android app from dashboard configuration to a controlled Google Play testing release.
Before you start
- Completed APK and AAB build
- Google Play Console app with matching package name
- Privacy policy and store assets
Configure and verify
Freeze release configuration
Review app name, URL, identifier, icon, style, modules, permissions, SDK credentials, signing, version, and URL rules.
Test the APK
Use at least one older supported device and one current Android device. Test fresh install, upgrade, login, logout, files, camera, media, push, deep links, back behavior, rotation, offline recovery, and external links.
Review privacy and policy
Match Play Data safety answers to actual SDKs and permissions. Add consent flows and required disclosures.
Upload the AAB to internal testing
Use a higher version code, upload the AAB, resolve Play warnings, and distribute it to licensed testers.
Retest the Play-installed build
Google Play signing can change certificate fingerprints. Recheck Google Sign-In, Firebase, App Links, Billing, and other certificate-bound services.
Promote gradually
Move from internal to closed or open testing before production and monitor crashes, WebView errors, downloads, login, and notification delivery.
Store assets
- High-resolution icon
- Phone and tablet screenshots when applicable
- Short and full descriptions
- Feature graphic
- Privacy policy URL
- Support contact
Version discipline
Test before release
- APK device matrix passed
- AAB internal test passed
- Data safety matches behavior
- Play signing fingerprints are registered
- Rollback and support plans exist