Prerequisites Before Publishing

Before starting the Play Store submission process, make sure you have:

Step 1 — Generate a Release Keystore

Your release keystore is the cryptographic key that signs your app and proves it came from you. Keep this file safe forever — losing it means you can never update your app on the Play Store.

# Run this in your terminal keytool -genkey -v -keystore ~/upload-keystore.jks \ -storetype JKS \ -keyalg RSA \ -keysize 2048 \ -validity 10000 \ -alias upload
⚠️ Critical: Store your keystore file (.jks) and passwords in a secure location. Never commit them to Git. Losing your keystore means you cannot push updates to your existing Play Store app.

Step 2 — Configure App Signing in Flutter

Create a file named key.properties in the android/ folder of your Flutter project:

storePassword=YOUR_STORE_PASSWORD keyPassword=YOUR_KEY_PASSWORD keyAlias=upload storeFile=/Users/yourname/upload-keystore.jks

Then update android/app/build.gradle to reference this file for release builds. This tells Flutter to sign your release APK/AAB automatically.

Step 3 — Build the Release App Bundle (AAB)

Google Play now requires App Bundles (.aab) instead of APKs. Build yours with:

# Build the release App Bundle flutter build appbundle --release

Your AAB will be generated at: build/app/outputs/bundle/release/app-release.aab

💡 Tip: Run flutter build appbundle --release --obfuscate --split-debug-info=build/debug-info to obfuscate your Dart code, protecting your intellectual property.

Step 4 — Set Up Google Play Console

1

Create New App

Log in to play.google.com/console → "Create app" → Enter app name, default language, app/game type, and free/paid status.

2

Complete Dashboard Tasks

Play Console shows a "Set up your app" checklist. Complete all required sections: testing, content rating, data safety, target audience, and app content.

3

Create Internal Testing Release

Before submitting to production, create an Internal Testing release and upload your AAB. Test with real testers to catch any issues.

4

Promote to Production

Once internal testing is confirmed working, promote to Production. You can do a staged rollout (e.g. 10% of users first) or full rollout.

Step 5 — Create the Store Listing

Step 6 — Submit for Review

Once all required sections are complete, click "Send for review". Google will review your app — typically within 1–3 days for new apps. You'll receive an email when approved or if there are issues.

💡 Timeline expectation: First-time app submissions often take 3–7 days. Subsequent updates to an approved app typically review in 1–2 days. Expedited review is not available.

Common Rejection Reasons & How to Avoid Them

Don't Want to Deal with All This?

We handle the entire Play Store publishing process for you — included free with every app we build.

Build + Publish My App from $49

FAQ — Flutter Play Store Publishing

New apps typically take 1–3 days. Occasionally up to 7 days if additional review is triggered. Updates to already-published apps are usually reviewed faster, within 1–2 days.
Yes, there's a one-time $25 USD Google Play Developer Account registration fee. After that, publishing unlimited apps is free. Google takes 15–30% commission on paid apps and in-app purchases.
Yes. Every app built by FlutterAppDeveloper.online includes complete Play Store publishing at no extra charge. We handle everything from AAB generation to getting your app live — you just need a Google Play Developer Account ($25 one-time fee).
APK (Android Package) is the traditional format. AAB (Android App Bundle) is Google's newer format that allows Play Store to deliver smaller, optimized APKs to each device. Google now requires AAB for new apps. Flutter supports both — use 'flutter build apk' for APK or 'flutter build appbundle' for AAB.