Short answer: the clock is per tester. Google says testers who opt in, test for fewer than 14 days and then opt out don't count, and if a tester opts out and back in later, their 14 days must be consecutive. So an individual tester's clock restarts when they opt out. Uploading a new build is not described as a reset and is encouraged.
Think in tester-days, not one project clock
Many developers imagine a single 14-day timer for the whole app. Google's wording is about each tester: at least 12 testers must have been opted in continuously for the 14 days before you apply. If you started on day 1 with 12 people and one left on day 10, you have 11 qualifying testers on day 14 and need someone else to complete their own 14 days.
Things that do break a tester's streak
Opting out
Tapping "Leave the program" on the opt-in page ends their continuous period.
Being removed from your list or Google Group
If you delete a tester from the email list or they leave the group, their access to the track is gone. Be careful when tidying lists mid-test.
Things that don't reset anything
Uploading new builds
Google encourages updating your app during closed testing to fix reported issues.
Changing release notes or the store listing
These don't affect opt-in status.
Uninstalling, as far as Google's article describes
The article talks about opt-in, not installs. But a tester who uninstalls isn't engaging with your app, and engagement is assessed too, so treat an uninstall as a warning sign.
How to protect your count
Recruit a buffer of three to eight extra testers. Keep a sheet with each opt-in date and check it every few days. Message quiet testers with a small task. Don't remove anyone from the list until your production access is approved. TestLancer has a dedicated explainer on the closed testing clock.
Planning around a reset
If you discover on day 12 that you're down to 10, add new testers immediately. They need their own 14 consecutive days, so your earliest application date moves to 14 days after they opt in. Starting with a buffer avoids this two-week delay.
The official rules, in one place
According to Google's Play Console Help article on app testing requirements for new personal developer accounts:
- The rule applies to personal developer accounts created after November 13, 2023.
- You must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days.
- Production and Pre-registration stay disabled until you meet the requirement; you then apply for production access from the Dashboard.
- The application has three parts: About your closed test, About your app/game and About your production readiness.
- Review usually takes seven days or less, but can take longer. If engagement was too low or you had fewer than 12 opted-in testers, Google may ask you to keep testing.
- Testers who opt out before 14 days don't count, and if someone opts out and back in, their 14 days must be consecutive.
Quick checklist before you apply for production access
- [ ] At least 12 testers opted in today, each for 14 or more days in a row (check your log, not your memory).
- [ ] A buffer of extra testers in case someone drops out at the last minute.
- [ ] Notes on which features testers used, and whether that matched how you expect real users to behave.
- [ ] A short summary of the feedback you received and how you collected it (Play testing feedback, a form, a chat group).
- [ ] A list of changes you made because of the test, with version numbers.
- [ ] Working test credentials in Play Console if your app needs a login.
- [ ] Content rating, target audience and data safety answers that match the real app.
- [ ] No crashes or empty screens on the build you're about to ship.
If any box is empty, a few more days of testing usually costs less than another review cycle.
Mistakes that cost developers extra weeks
- Recruiting exactly 12. One opt-out and you're back to waiting.
- Running the test on the internal track. Internal days don't count toward the requirement.
- Sharing an APK instead of the opt-in link. Testers must opt in and install from Google Play.
- Tidying the tester list mid-test. Removing someone ends their streak.
- Shipping no updates. The production readiness section asks what you changed because of testing.
- Using friends who never open the app. Google can ask for more testing when engagement is low.
- Buying reviews or ratings. They break Google Play policy and give you nothing to report. TestLancer never sells them.
FAQ
If a tester changes phones, do they reset?
Opt-in is tied to their Google account, not the device. Ask them to install from Google Play on the new phone with the same account.
Can I see opt-in dates in Play Console?
Keep your own log as well, since it's the simplest way to know who qualifies on a given day.
Does a paused or halted release reset testers?
Google's article doesn't describe that. Keep testers opted in and an installable build on the track to be safe.
Next step
If you can't find 12 reliable people on your own, TestLancer's Google Play closed testing service runs a 14-day closed test with real testers who opt in, use your app and send feedback you can summarise in your production access application. You can also use the free Google Play Launch Center checklist first. TestLancer does not sell reviews, ratings or installs, and no one can guarantee Google will approve production access. Your app still has to meet Google Play policy.
Top comments (0)