Getting a Flutter app through Google Play closed testing
New personal developer accounts cannot go straight to production. Here is the checklist we follow to get from a signed bundle to a public listing without surprises.
If you open a new personal developer account on Google Play, you cannot publish straight to production. You first have to run a closed test with at least 12 testers who stay opted in for 14 days in a row. Only then can you apply for production access.
We have taken several apps through this now, starting with StressPop. This is the checklist we follow.
1. Sort out signing before anything else
Create an upload keystore, keep it somewhere safe, and back it up. Google Play App Signing holds the real app signing key, but you still need the upload key for every release. Losing it means a support request and a delay.
In Flutter, point android/key.properties at the keystore and build the bundle:
flutter build appbundle --release
2. Fill in every policy section first
The Play Console will not let you roll out a release until these are done:
- App content: privacy policy URL, ads declaration, target audience and content rating
- Data safety: what you collect, why, and whether it is shared
- Store listing: app icon (512 x 512), feature graphic (1024 x 500) and phone screenshots
Write the privacy policy so it matches what the app really does. If you use AdMob, say so and link to Google's policy. Reviewers compare the data safety form with the permissions and SDKs in your bundle.
3. Recruit testers who will actually stay
The 14 days only count while at least 12 testers remain opted in. Friends who install once and leave the test do not help. We send testers the opt in link with a short note explaining why it matters, and check the tester count every few days.
4. Ship real updates during the test
When you apply for production, Google asks what you learned during testing and what you changed. Push a couple of small updates during the 14 days: crash fixes, copy changes, a layout tweak. It gives you honest answers for the application.
5. Apply, then wait
Production access reviews usually take a few days. Once approved, promote the tested release to production and the listing goes live.
The rule feels slow the first time. By the second app it is just part of the plan: we start recruiting testers while the app is still being built.
