Since late 2023, Google requires new personal developer accounts to run a closed test before they can publish to production. The current requirement is 12 testers opted in continuously for 14 days. It exists to filter low-effort submissions, and it works — but it also catches legitimate first-time publishers who planned a launch for next week. This guide is how to get through it efficiently.
Who it applies to
- Personal accounts created after 13 November 2023, for their first app. After production access is granted once, later apps don't repeat it.
- Not organisation accounts.
- Not accounts created before that date.
Setting up the track
- Console → Test and release → Testing → Closed testing → create a track (the default "Alpha" is fine).
- Upload your AAB. It goes through a light review before the test link becomes active — usually hours, sometimes a day or two.
- Testers: add by email list or by Google Group. Use a Group: you can add and remove people without editing the console, and one link serves everyone.
- Copy the opt-in URL and the Play Store link the console shows. Testers must open the opt-in URL, accept, then install from Play. Installing your APK directly does not count.
- Fill the country availability (at least the testers' countries) and the store listing basics — the test track still needs a listing.
Recruiting testers who stay
The requirement is 12 opted in continuously. If someone opts out on day 9, your count drops and, if it falls below 12, the clock effectively restarts. So:
- Recruit 15–20, not 12.
- Explain in one message what to do: open link → Become a tester → Install → keep it installed for two weeks. Say plainly "please don't uninstall until I say so".
- Prefer people with Android phones they use daily — a spare phone in a drawer gets reset.
- Family, colleagues, regular customers, a community you belong to. Paid tester-exchange services exist; they work, but the testers are strangers with no interest in your app, and Google's questionnaire asks what feedback you received.
- Check the console's tester count every few days.
What to test during the fortnight
Don't waste the two weeks waiting. This is your real-device test of the Play-signed build:
- Fresh install from Play: splash, first page, no browser bar.
- Aeroplane mode: offline screen with retry, not a raw error.
- Back gesture from the first screen: exit confirmation.
- Every menu item; external links open where you intended.
- Push: send a test notification from OneSignal; confirm delivery and the deep link.
- Rotate; open on a tablet if anyone has one.
- Read the pre-launch report (Console → Test and release → Pre-launch report): Google runs the build on real devices and reports crashes, accessibility issues, security warnings and screenshots from each device. Fix anything red before applying for production.
- Collect feedback in writing — you will be asked to summarise it.
You can upload new versions to the track during the period; that does not reset the 14 days as long as testers stay opted in.
Applying for production access
When the console shows the requirement met, an Apply for production button appears on the dashboard. The questionnaire asks: how you recruited testers, how they used the app, what feedback you received, what you changed, and whether the app is ready. Answer specifically and honestly — "12 friends installed it and said it was fine" is a weak answer; "17 customers of my bakery tested ordering over two weeks; two reported the menu images loaded slowly on 3G, so we compressed them; one asked for order-ready notifications, which we added" is a strong one. Google responds in a few days. Rejections of the application are usually about thin answers and can be reapplied for after fixing.
Pitfalls that cost weeks
- Testers installing an APK you sent instead of opting in through Play — they don't count.
- Making the test track available only in a country none of your testers are in.
- Letting the count dip below 12 and not noticing for a week.
- Uploading a bundle with a lower version code than the previous one.
- Treating the questionnaire as a formality.
Internal testing, for context
Internal testing (up to 100 testers, live within minutes, no review) is separate and available immediately. Use it for your own devices and your team before the closed track; it does not count toward the 14-day requirement.