What “14 continuous days” means
Every day in the period must have 12 or more testers opted in. Not on average. Not on most days. Every day. The period begins the moment the twelfth tester opts in, and if the count drops below 12 at any point, the count of continuous days returns to zero.
Google does not tell you when this happens. There is no alert in Play Console and no email. The first sign is usually that the production access application never appears.
A run that broke on day nine
One tester changed phone on day nine. The count went to 11, the period reset, and eight days of waiting bought nothing. Running with 14 testers instead of 12 is what prevents this.
What is safe—and what resets it
Safe during the run
- Shipping new builds to the closed track
- Editing your store listing
- Adding more testers
- Replying to tester feedback
- Running an internal test alongside
Resets or breaks the run
- Removing testers from the tester list
- Halting or unpublishing the rollout
- Deleting or recreating the closed track
- Letting the opted-in count fall below 12
- Switching to a different track mid-run
Shipping updates is not only safe, it helps. The production access questionnaire asks what you changed in response to feedback, and a release dated mid-period is the cleanest evidence you can give.
A realistic timeline
Days −3 to 0: setup
Create the closed track, upload a signed release, roll it out, and wait for Google’s review of that first build. This usually takes hours and can take a couple of days. None of it counts toward the 14.
Day 0: the twelfth opt-in
Testers open the opt-in link, accept, and install from the Play Store. When the twelfth completes that, the clock starts.
Days 1–7: the quiet half
Nothing is required of you. This is where drop-off begins, so check the opted-in count in Play Console at least once. If it has fallen, top up immediately — the sooner you are back above 12, the sooner the count resumes.
Days 8–13: the fragile half
Losing a tester on day twelve costs you everything you have banked. Keep spare testers on the list, and do not touch the rollout.
Day 14: eligible
The production access application appears on the Play Console dashboard. What it asks and how to answer it.
Days 15–16: buffer
Applying on the exact boundary invites a refusal on a technicality. Keep testers in place two extra days and apply from a position where the requirement is unambiguously met.
The one thing that decides it
Not the app, not the feedback, not the questionnaire. Whether twelve people were still there on day fourteen. The full requirement, and who it exempts.