"Apply for Production" Still Disabled After 14 Days? Here Is Why
Updated 27 September 2026
The button unlocks only when Play Console has recorded at least 12 testers who stayed opted in to your closed test for 14 days in a row. If it is still disabled, the usual causes are: the count dropped below 12 on some day (which restarts the 14 days), Play Console has not refreshed yet (allow 24-48 hours), or the testers were on internal testing or an inactive track instead of an active closed testing track.
What Google actually checks
For personal developer accounts created after 13 November 2023, Google requires a closed test with at least 12 testers who have been opted in for the last 14 days continuously. Play Console tracks this for you: open Dashboard and look for the "Apply for production" section, which shows how many testers are opted in and how many days are complete.
The rule is about testers being opted in continuously, not about how many people ever joined. A tester who leaves the test, or whose Google account is removed from the tester list, stops counting from that day.
The common causes, in order of likelihood
- 1The tester count dipped below 12 on some day. If even one day had 11 opted-in testers, the continuous 14 days start again from the next day. Check the daily numbers in the Dashboard section; this is why services keep more than 12 testers as a buffer.
- 2Play Console has not caught up. The counter and the button can lag by a day or two after the 14th day. Wait 24-48 hours before assuming something is wrong.
- 3The testers are on the wrong track. Only an active closed testing track counts. Internal testing, open testing, or a closed track with no rolled-out release does not.
- 4Your tester list changed. Removing the Google Group or email list from the closed track, or swapping it for another, removes those testers from the count.
- 5The release is not live on the track. If the closed testing release was halted, rejected or never rolled out, testers cannot stay opted in to a working app.
How to fix it
- Open Play Console → Testing → Closed testing → your track, and confirm a release is rolled out and the tester Google Group is still listed on the Testers tab.
- Check the opted-in count in the Dashboard's production access section. If it is below 12, add testers and expect a fresh 14-day run.
- If the count has been 12 or more for 14 days, wait a day for the dashboard to refresh before contacting Google support.
- Do not delete and recreate the closed track to "reset" it; that removes your testers from the count.
How we prevent this
Every 12Tester Community plan keeps extra testers above the minimum (15 or 20 on Medium and Pro) and runs the test for 14 days plus buffer days, so a single tester dropping out never takes your count below 12.
Frequently asked questions
Does the 14-day counter restart if the tester count drops below 12?
Yes. The requirement is 12 testers opted in for 14 continuous days, so a day below 12 means the 14 days are counted again from that point.
How long after day 14 does the Apply for production button appear?
Usually on the day the requirement is met, but Play Console can take 24-48 hours to update. Check again the next day before changing anything.
Do internal testing testers count toward the 12?
No. Only testers on an active closed testing track count toward the production access requirement.