You counted 14 days. The Console still does not offer production access. Something in the count does not match your calendar.
The requirement is not "14 days since I started the test." It is at least 12 testers, each opted in for 14 continuous days, in a qualifying closed test. If any part of that is off, the production button stays unavailable.
Check 1: is every required tester at 14 days?
Each tester has their own clock. If your first 10 testers opted in on day one and two more joined on day four, the group is not complete until those two have also completed 14 continuous days.
Look at the latest opt-in date among the testers you need. That is the real finish line.
Check 2: are there still 12 eligible testers?
A tester who opted out, was removed, or switched accounts may no longer count. If the group dropped below 12, the Console will not show eligibility even if 14 days have passed since the original start.
Compare the current tester list with your tracker.
Check 3: is the test on the closed track?
Internal testing and open testing are different tracks. A 14-day internal test does not satisfy the closed-testing requirement.
Open Testing → Closed testing and confirm the test you ran is there.
Check 4: is the track still active?
A paused track, a rejected release, or a removed build can affect the test. Check the track and release status.
The 14 days are about opt-in continuity, but an inactive test can leave you without the evidence or the active track the application expects.
Check 5: does the account actually need this?
The 12-tester requirement applies to covered personal accounts created after 13 November 2023. Organization accounts and accounts that already had production access before the change are generally not covered.
If your account is not covered, the production-access requirement may not appear at all. That is not a bug.
Check 6: has the Console updated?
Tester counts and eligibility can lag. Refresh the page, sign out and back in, and check again after a short wait.
If the tester count is correct and the days are complete but the button is still missing, move on to support rather than refreshing for hours.
Check 7: is another requirement blocking you?
Production access can be blocked by more than the closed test. Check for:
- incomplete app content declarations;
- a policy violation or rejected release;
- account verification issues;
- an unpublished or removed app;
- a pending review;
- a payment or developer account problem.
The Production page usually tells you what is missing. Read the whole page, not just the button.
What to send support
If you have checked everything, contact Google Play developer support with:
- the app package name;
- the closed track name;
- the tester count;
- the first and last opt-in dates;
- screenshots of the tester list and requirement status;
- a short explanation of what is missing.
Keep it factual. "I completed 14 days but the button is not available" plus evidence is easier to investigate than a long complaint.
The short version
- 14 days from the start is not the same as 12 testers each completing 14 days.
- Check the latest opt-in date, current count, track, and account type.
- Look for other production-access blockers.
- Contact support with evidence if the Console still disagrees.
Next: why the production access button is greyed out or how to apply for production access.
Our team’s note
If this answered the question but your situation still feels messy, send us the screenshot or the rejection email. Some things are easier to solve in a two-minute conversation than another article.