Guide · the 14-day requirement
How Google Counts the 14 Days of Closed Testing
The requirement sounds simple — 12 testers, 14 days — but the details (dropouts, late joiners, updates) are what cost people weeks.
What Google says
Google requires a minimum of 12 testers who have been opted in continuously for at least 14 days. It also specifies that testers who opt in, test for fewer than 14 days and opt out do not count, and that if someone opts out and later opts back in, the 14 days must be consecutive. Official source: Play Console Help, “App testing requirements for new personal developer accounts”.
What developers report (not published by Google)
Several guides and forums describe the Play Console counter as a count of consecutive days with at least 12 opted-in testers, and claim that if the number drops below 12, even for a few hours, the counter pauses or resets. Google does not spell this out in its documentation, so treat it as a prudent warning: it is why you should never sit at exactly 12.
Common cases
- Testers who start on different days: each one needs their own 14 consecutive days. You can apply for production when the 12th-oldest tester reaches theirs.
- A tester opts out or uninstalls: they may stop counting and their replacement starts from zero. With 14–16 testers, one dropout does not leave you below 12.
- A tester never accepted the invitation: Google does not notify them when you add them to the list; the tester must open the opt-in link with the added account.
- Updating the app: we have not found in the official documentation that publishing a new build resets the period. Always check your Play Console counter.
- Internal testing does not count toward this requirement: only closed testing does.
Do testers have to open the app every day?
What counts for the requirement is continuous opt-in, not opening the app daily. But the production form asks about testers' real usage, so it is wise to have them use the app over several days and go through the main flows.
How Tester Marketplace handles it
We count each tester's streak from their first recorded session (the best evidence they accepted the invitation and installed the app), show you the estimated date you could apply for production and warn you if it slips. It is an estimate: we cannot see your Play Console, so always trust its counter.
Frequently asked questions
What happens if a tester opts out mid-test?
According to Google, anyone who opts out before 14 days does not count. Also, developers report that if the total falls below 12 the counter may reset. Having 14–16 testers gives you a buffer.
Can the 12 testers start on different days?
Yes, but each one needs their own 14 consecutive opted-in days. You can apply for production once the 12 required have completed theirs.
Does updating the app reset the 14 days?
We have not found in the official documentation that it does, but we do not guarantee it: verify the counter in your Play Console after publishing a build.
Does internal testing count toward the 12 testers?
No. Only closed testing counts toward the production access requirement.