Prepare release identity first
Follow the Flutter Android deployment guide. Verify application ID, version name/build number, icon and release signing before creating the artifact.
Keep the upload keystore and passwords private. Play App Signing separates the upload identity from the certificate used for APKs delivered to users.
Build the intended app bundle
flutter build appbundle --release
Use the selected flavor and entry point when the project has them. Record the generated artifact path from the build output rather than uploading an older similarly named file.
Do not rely on debug-only network permissions, endpoints or plugin behavior.
Complete the Play release requirements
The Play release guide covers track creation and release preparation. Check the current target API requirement, app access instructions, Data safety, content rating and any account-specific testing requirements.
A successful upload does not mean the release is approved, rolled out or visible to every country.
Test the Play-delivered build
| Feature | Why test after Play delivery |
|---|---|
| Google/Firebase sign-in | Distributed signing certificate |
| Billing | Store and account environment |
| Native plugins | Device-specific packaged libraries |
| Asset loading | Bundle/device delivery behavior |
| Crash reporting | Correct release identity and symbols |
Use a supported test track and eligible tester account. Internal App Sharing has different signing behavior and is not identical to an internal testing track.
Retain a release record
Archive source revision, Flutter version, dependency lockfiles, signing fingerprint, AAB hash and diagnostic symbols. APKLint's Flutter, bundle and release-checklist tools can support artifact review; they cannot approve a Play submission or verify private console declarations. Keep actual test and review outcomes with the release before expanding availability.
Sources and further reading
- Flutter: Build and release an Android app
- Google Play: Prepare and roll out a release
- Google Play: Use Play App Signing
Reference review: 22 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.
Android inspection tools and practical release guides. About APKLint · Report a correction
