Use an Android App Bundle for your Google Play release workflow. Complete branding, production configuration, release signing, and testing first.
Set the version in pubspec.yaml, for example 2.0.1+7, using values appropriate for your release history. The number after + is the Android build/version code; it must advance for subsequent store uploads.
Run:
The usual output is build/app/outputs/bundle/release/app-release.aab. Flutter documents bundle creation in its Android release guide.
Upload the bundle to an appropriate test track in your Play Console application. Install the store-delivered test version and repeat the customer workflows, including network access and push notifications.
An AAB is an input to the distribution pipeline, not a file customers install in the same way as an APK. Use the store test workflow to verify the generated application delivered to devices.
If upload fails, check the reported application ID, version code, and signing certificate. Resolve the actual mismatch instead of generating a new application ID or keystore for an existing published app.
Retain the bundle, source revision, and release notes for the uploaded build.