If the Apply for production button is missing after 14 days, the most likely reason is that Play Console doesn't count 14 days yet. Your own calendar and Google's count often start on different days, and any day below 12 opted-in testers breaks the streak.
This is one of the most common questions from developers at the end of a closed test. Here is where the button should be, the reasons it doesn't show up, and what to do about each one.
Where the button should be
Open Play Console, select your app and go to its Dashboard. For personal accounts that need closed testing, the Dashboard shows the closed testing requirement with your progress: how many testers are opted in and how many days have passed. Once both conditions are met, that is where Apply for production appears.
Make sure you are looking at the right app. If you have more than one app in the account, each one has its own closed test and its own count. Testers on app A don't help app B.
Reason 1: your 14 days started later than you think
The count doesn't start when you create the closed track or share the opt-in link. In practice it starts on the day you first have at least 12 testers opted in. If testers trickled in over the first week, your 14 days may have started on day 6 of your own calendar.
Look at the progress on the Dashboard rather than your own notes. If it says fewer days than you expected, this is almost always why. The fix is simply to keep testers opted in until the count reaches 14.
Reason 2: you dropped below 12 at some point
The requirement is 12 or more testers opted in for 14 days in a row. If someone opted out and your count fell to 11, even for a day, the streak may have been broken. A tester who removed themselves from your Google Group or email list, or who left the test from the Play Store, counts as gone.
Check your opted-in count now. If it is below 12, recruit replacements first. Keep a buffer above 12 so one drop-out doesn't cost you days again. If you need replacements quickly, PeerPlay is built for this: Android developers test each other's apps every day, through your real closed track.
Reason 3: testers aren't really opted in
A tester on your list is not the same as an opted-in tester. Each tester has to open your opt-in link and accept it with the same Google account that is on your list. Testers who only received an invite, or accepted with a different account, don't count.
Also check that your closed track has a release that is actually available to testers. If the release is still in review or was never rolled out, testers can't properly join the test.
Reason 4: your account doesn't need it
Not every account sees this flow. As far as Google documents it, the closed testing requirement applies to personal developer accounts created on or after November 13, 2023. Organization accounts don't have it, so there is no Apply for production step: they can publish to production directly.
If you have an organization account or an older personal account, look for the Production track instead of waiting for a button.
If everything looks right
If the Dashboard shows 12 or more testers and 14 days, and the button still isn't there, give it a day. Play Console counts aren't always updated in real time. If it is still missing after that, contact Play Console support from the Help menu with screenshots of your tester count and track.
When the button does appear, the application asks how you ran the test, what feedback you got and what you changed. Prepare those answers during the 14 days, not after.
Top comments (0)