If you opened a personal Google Play developer account after November 13, 2023, there is a step between "my app is ready" and "my app is live" that surprises a lot of people. You cannot publish to production at all until you have run a closed test with at least 12 testers for at least 14 days.
The rule is short. The way it is counted is where people lose two weeks. This post walks through it using Google's own wording, then gives a timeline that works the first time.
The rule, in Google's words
Google's help page "App testing requirements for new personal developer accounts" says developers with personal accounts created after November 13, 2023 must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days. Until then, Production and features such as Pre-registration stay disabled in Play Console.
Organization accounts, and personal accounts created before that date, are not subject to it.
The two words that matter: "continuously" and "preceding"
The page says at least 12 testers must be opted in when you apply, and they must have been opted in continuously for the preceding 14 days.
That has two consequences:
- A tester who joins on day 10 has not been opted in for 14 days on day 14. They don't count yet.
- A tester who opts out on day 9 and back in on day 11 breaks their own streak.
So 12 is the floor, not the target. The safe plan is to recruit more than 12, so that a few drop-outs do not reset your clock. Invite 15 to 20 people, and get everyone in during the first day or two.
The four tracks, briefly
Google Play doesn't have one upload button. It has four tracks under Test and release:
| Track | Audience | Good to know |
|---|---|---|
| Internal testing | Up to 100 testers you list by email | Can run before app setup is finished; builds usually reach testers within seconds |
| Closed testing | Testers you choose, by email lists or Google Groups | Starts after app setup is complete; required before production for new personal accounts |
| Open testing | Anyone who finds and joins the test | Available once you have production access |
| Production | Everyone on Google Play in your chosen countries | Locked for new personal accounts until production access is approved |
One detail catches people out: internal testers cannot also be in your closed test. A user who opts in to your internal test is no longer eligible for an open or closed test. To join the closed test they must first opt out of the internal one. If you plan to be one of your own 12 closed testers, opt out of the internal test before the closed test begins.
Also, the first test link can take several hours to become available after you publish a test for the first time. Plan your invitations around that.
Set up the closed test
- Finish the app setup tasks in Play Console. You can start a closed test only after completing app setup.
- Go to Test and release, then Testing, then Closed testing, and create or manage the closed track.
- On the Testers tab, choose Email and select an email list, or choose Google Groups and enter a group address like
yourgroupname@googlegroups.com. - Create a release on the closed track with your bundle (a new versionCode if it is a new build) and roll it out.
- Check the countries and regions the test is available in.
- Once the test is live, copy the opt-in link and send it to your testers.
Use a Google Group rather than an email list. You add people to the group once, they join and leave through the group itself, and you never edit the tester list in Play Console again. Use a group that only you can add members to, so the test stays closed.
Tell testers about the 14 days
Google's guidance marks this as important: tell testers they need to stay opted in for at least 14 days. Most drop-outs happen because a tester tidied up their apps. Give them something to do as well. A short message covers it:
Thanks for testing Torchlight!
1. Open this link on your Android phone and tap "Become a tester":
<your opt-in link>
2. Install Torchlight from the Play Store page that opens.
3. Please stay in the test for at least 14 days. Uninstalling is fine,
but don't leave the test, or Google stops counting you.
4. Try: turn the torch on and off, turn it off from quick settings,
press Home while it's on, open the camera app and come back.
5. Anything odd? Send private feedback on the Play Store page
or email me at <your address>.
Use the 14 days, don't just wait
The test is not a waiting room. Google asks you to respond to feedback and fix bugs during the test, and the production application asks what you changed. Keep a simple log: date, what a tester reported, what you did. Shipping one or two updated builds to the closed track during the 14 days is normal, and every new build needs a higher versionCode.
The production application
When at least 12 testers have been opted in for the preceding 14 days, the Dashboard offers Apply for production. The form has three sections:
- About your closed test: how easy it was to recruit testers, whether they used all features, whether usage matched real-world use, and a summary of the feedback.
- About your app or game: the target audience as specifically as possible, how the app provides value, and an estimated install range for the first year (not shown publicly).
- About your production readiness: what you changed based on the test and how you decided the app was ready.
Answer from your log. "Testers reported that the button stayed on 'Turn off' after using the quick settings tile; I added a torch callback in version 1.0.1 so the screen follows the real flash state" is the kind of answer the questions are designed for. "Testers liked it" gives the reviewer nothing to approve.
Don't leave the form half-done. Google warns that if you click Discard or leave a section without clicking Next (or Apply on the last section), your changes are not saved.
The whole timeline
| When | What you do |
|---|---|
| Day 0 | Account verified, app created, setup tasks done |
| Day 0 | Internal test with yourself; install from Play and test |
| Day 0 to 1 | Closed test live; send the opt-in link to 15 to 20 people |
| Days 1 to 14 | Keep testers engaged, collect feedback, ship fixes with higher versionCodes |
| Day 15 or later | At least 12 testers opted in for 14 straight days; apply for production |
| Up to about a week later | Google's decision by email; production unlocks |
Google says review usually takes seven days or less but can occasionally take longer. If Google decides the app needs more testing, the reasons it gives include having fewer than 12 opted-in testers or insufficient tester engagement. So recruit extra people, keep them busy, and apply with real answers.
This is adapted from my book Ship Your First Android App (Android the Right Way, Book 1). The free sample is here and the full book is here.
Drafted with AI help and edited by the author; based on his book.
Top comments (0)