The 12 testers for 14 days requirement, explained

If you created a personal Google Play developer account after 13 November 2023, you cannot publish to production until you have run a closed test with at least 12 testers opted in, continuously, for 14 days.

That is the whole rule in one sentence, and almost everything that goes wrong with it comes from four words: personal, opted in, continuously, and 12. This guide takes each one apart, because every support question we get is a misreading of one of them.

Who the requirement applies to

It applies to personal developer accounts created after 13 November 2023. It does not apply to:

• Organization accounts. If you registered as a company with a D-U-N-S number, you are exempt. This is the single most common reason one developer swears the requirement does not exist while another is stuck behind it.
• Personal accounts created before 13 November 2023. Grandfathered.

If you are not sure which you have, Play Console shows the account type under Setup. Check before you spend two weeks on something you may not need.

What "opted in" actually means

There are three states a person can be in, and only the third one counts:

1. Invited. You added their email to the closed testing track, or they are in a Google Group you attached. Counts for nothing.
2. Installed. They have the app on a device. Also, on its own, counts for nothing.
3. Opted in. They followed your opt-in link — the web URL Play Console gives you under Testing → Closed testing → Testers — and accepted. This is the one Google counts.

The gap between 1 and 3 is where most failed tests die. You send twelve invitations, eleven people say "yeah I've got it", and Play Console shows four. They installed from a link you sent, or they accepted the Google Group invite and stopped there. See how to verify a tester actually opted in for how to check this properly rather than by asking.

What "continuously" costs you

The 14 days are a stretch during which your cohort was intact, not a tally of qualifying days. If you are at 12 on day one and someone drops to 11 on day six, you have not banked six days towards a total — you have a gap in the middle of the window you were trying to prove.

Two practical consequences:

• Recruit more than 12. Thirteen or fourteen testers costs you nothing and covers you for one person's phone dying, one uninstall and one silent drop-out. Nothing in the policy penalises a larger cohort, and TestersWiz places no cap on how many testers a campaign takes for exactly this reason.
• Check the count more than once. Play Console shows the current number of opted-in testers, not a history. If you only look on day 14 you have no way of knowing whether you dipped to 11 on day six.

What to do the day someone leaves is covered in what happens if a tester opts out.

What does not reset the clock

Two things developers worry about far more than they need to:

• Uploading a new build. Shipping an update inside the window does not restart the 14 days, and Google's guidance actively wants to see iteration during a test. The long version is in does a new build reset the clock.
• Testers not opening the app every day. The requirement is about being opted in, not about daily engagement. A tester who installs, opts in and forgets about it still counts.

Closed testing, not internal testing

Internal testing is a different track with a different purpose, and it does not satisfy this requirement no matter how many people you put in it. If you have been running an internal test for three weeks, that time does not transfer. Closed vs internal testing sets out which is which.

The sequence, start to finish

1. Create a closed testing track in Play Console and upload a release to it.
2. Add testers by email list or Google Group, and copy the opt-in link.
3. Get 12+ people to follow that link and accept. Verify the count in Play Console rather than trusting replies.
4. Wait 14 continuous days, checking the count every few days.
5. Apply for production access.
6. Keep everyone opted in until access is actually granted. Google reviews the application after the 14 days, and the review is not instant.

Step 6 is the one that catches people who did everything else right. The moment your fortnight is up is not the moment you are done — it is the moment you can apply.

Finding the 12 people

This is the actual problem, and it is a social one rather than a technical one. Twelve humans who will install an unfinished app and leave it installed for two weeks is a real ask, and most indie developers do not have twelve friends with Android phones.

The realistic options are: people you know, a developer community where the exchange is understood, or a paid service. We are the second kind — TestersWiz is a free test-for-test exchange where you test another developer's app and they test yours, with the opt-in verified against Play Console on both sides. If you want the honest case for each route, including when paying is the better call, see free vs paid app testers.

Whichever way you go, the rule you are satisfying is the same one: twelve, opted in, fourteen continuous days, then apply.