Google Play's 12-tester rule: why your 14 days reset

You finished the app, built a signed bundle and opened Play Console, ready to ship. Then the Production page is locked. Ship Your First Android App gives this its own chapter, because it is the one step in publishing that comes with a calendar attached and no amount of coding speeds it up.

The rule, in Google's words

Google's "App testing requirements for new personal developer accounts" page states it plainly: 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 November 13, 2023, are not subject to it.

The trap: two words that reset your clock

Most people read "12 testers, 14 days" and start counting from the day the test goes live. The words that matter are "continuously" and "preceding". 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 consequences:

• A tester who joins on day 10 has not been opted in for 14 days on day 14.
• A tester who opts out on day 9 and back in on day 11 breaks their own streak.
• Most drop-outs happen because a tester tidied up their apps.

So recruiting exactly 12 people is the fastest way to restart the clock. The safe plan is to recruit more than 12, so a few drop-outs do not reset you. The book's timeline sends the opt-in link to 15 to 20 people and gets everyone in during the first day or two.

The four tracks

Google Play does not have one "upload" button. It has tracks, all under Test and release in Play Console:

• Internal testing: up to 100 testers you list by email, for fast checks by a few trusted people. It can run before app setup is finished, and builds usually reach testers within seconds.
• Closed testing: testers you choose, by email lists or Google Groups. It starts after app setup is complete and is required before production for new personal accounts.
• Open testing: a public beta anyone can join on Google Play, available once you have production access.
• Production: the real release, locked for new personal accounts until production access is approved.

A few facts from Google's "Set up an open, closed, or internal test" page save confusion later. The first test link can take several hours to become available after you publish a test for the first time. And internal testers cannot also be in your closed test: a user who opts in to the internal test is no longer eligible for a closed or open test until they opt out of it. If you plan to count yourself as one of the 12, opt out of the internal test before the closed test begins.

The fix: set it up so the clock only runs once

Step 1, an internal test for yourself. Go to Test and release, then Testing, then Internal testing. On the Testers tab, create an email list with your own Google account. Create a new release, upload app-release.aab, add short release notes, save, and roll it out. Open the opt-in link on your phone, accept, and install from the Play Store. It is the first time you get the exact APKs Google Play generates from your bundle, signed with the app signing key.

Step 2, the closed test.

1. Finish the app setup tasks first; a closed test can only start after app setup is complete.
2. Go to Test and release, then Testing, then Closed testing, and create or manage the closed track.
3. On the Testers tab, choose an email list, or choose Google Groups and enter an address like yourgroupname@googlegroups.com.
4. Create a release with your bundle (a new versionCode if it is a new build) and roll it out.
5. Check the countries and regions the test is available in.
6. Once the test is live, copy the opt-in link and send it with instructions.

A Google Group is easier than an email list here. You add people once, they join and leave through the group, and you never edit the tester list in Play Console again. Use a group only you can add members to, so the test stays closed.

Tell testers the rule. Google's page marks it as important: inform testers they need to stay opted in continuously for at least 14 days. The book's sample message says it in one line: uninstalling is fine, but don't leave the test, or Google stops counting you. Give them clear steps to try and a feedback channel besides Play's private feedback.

Use the 14 days, don't just wait them out

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 each new build needs a higher versionCode.

Applying for production

When at least 12 testers have been opted in for the preceding 14 days, the Dashboard offers Apply for production. The application has three sections:

• About your closed test: how easy recruiting was, whether testers used all features, whether usage matched real-world use, and a summary of the feedback.
• About your app or game: the target audience, how the app provides value, and an estimated first-year install range (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, specifically. A bug a tester reported, the fix, and the version it shipped in is the kind of answer the questions are designed for; "testers liked it" gives the reviewer nothing to approve. And don't leave the form half-done: if you click Discard or leave a section without clicking Next (or Apply on the last one), your changes are not saved.

Google reviews the application and emails the account owner, usually within seven days, occasionally longer. If Google decides the app needs more testing, the reasons it gives include fewer than 12 opted-in testers or insufficient engagement. Review "is not a troubleshooting step": the app should already be stable, policy-compliant, rated correctly, and provide working login details under App access if it needs an account.

Checklist

• [ ] Account verified, app created, setup tasks done
• [ ] Internal test installed from Google Play on your own phone
• [ ] You opted out of the internal test if you count as a closed tester
• [ ] Closed test live with 15 to 20 people invited, all in during day one or two
• [ ] Testers told: stay opted in for 14 straight days
• [ ] A log of every report and fix, with builds using higher versionCodes
• [ ] 12 or more testers opted in for the preceding 14 days before you apply
• [ ] Every application section answered from the log, then Next or Apply clicked

Found this useful? Subscribe on YouTube for the daily video, or follow the RSS feed.