How to Apply for Production Access on Google Play
Where to click, what the three questionnaire parts ask and how to write answers that show a real closed test.
Read the guide →Google Play 'Apply for Production' Button Missing: Fixes
Quick answer The Apply for production button is missing because your closed test has not met Google's requirements yet: at least 12 testers opted in for 14 continuous days. Check setup, track, tester count, opt-outs and account type.
You have waited two weeks, your testers say they joined, and the Dashboard still shows no way to apply for production. That is one of the most stressful moments for a new developer, and it almost always has an ordinary explanation. This guide shows how to find yours in a few minutes: what Google says about who needs the test, the nine causes that hide the button, a quick check for each, and what to do next.
Why is the Apply for Production button missing?
Almost always, the Dashboard is telling you the closed test has not met Google's requirements yet. Google's testing requirements page says that personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers, each opted in continuously for at least 14 days, and then apply for production access from the Dashboard. Until then, the Production and Pre-registration features stay disabled. The rest of this guide helps you work out which requirement is missing in your case.
What do you see on the Dashboard?
Start from what is on your screen. Each row links to the fix further down.
| What you see | Most likely cause | Go to |
|---|---|---|
| No button, and tasks are still listed under Set up your app | Setup is not finished | Cause 1 |
| No closed test or no active release on the closed track | Test not published | Cause 2 |
| Closed test is live, but fewer than 12 testers show as opted in | Not enough testers | Cause 3 |
| Testers joined less than 14 days ago | The 14 days are not complete | Cause 4 |
| Testers joined but the count went down | Testers opted out | Cause 5 |
| You ran an open or internal test only | Wrong track | Cause 6 |
| An email or message says your application is being reviewed | Application already submitted | Cause 7 |
| Nothing mentions testing at all, and Production is open | Your account may not need the test | Cause 8 |
| Verification tasks or an Android device check are pending | Account verification incomplete | Cause 9 |
Does the closed testing requirement apply to your account?
| Account | What Google's page says |
|---|---|
| Personal account created after November 13, 2023 | Must meet the testing requirements before distributing apps. This is the group in this guide. |
| Personal account created before that date | Not addressed on the requirements page. Your Dashboard shows what you can do. |
| Organization account | Not addressed on the requirements page. Check your Dashboard and your account type. |
If you are unsure which account type you have, read our developer verification guide and the developer account fee guide. Google also says new personal accounts must verify access to an Android device through the Play Console mobile app, so that task can show up even when everything else looks done.
What are the 9 causes and how do you fix each one?
Cause 1: App setup is not finished
Google says setup must be complete before you can start a closed test. Open the Dashboard and finish every task listed in the setup section: store listing, content rating, target audience, Data safety, privacy policy and app access. See the content rating guide, the target audience declaration, app access instructions and the Data safety guide.
Cause 2: The closed test was never published
A track is not live until a release is rolled out to it. Open Testing > Closed testing, open your track and check that the release status is not a draft. If it is a draft, review and roll it out. If you need the upload steps, see how to create an AAB file.
Cause 3: Fewer than 12 testers are opted in
Adding an email address to a list is not the same as opting in. A tester must open your opt-in link and join with the right Google account. Compare your sheet with the number on the track. If you are short, recruit replacements now; read how to get 12 testers and how to share the closed testing link.
Cause 4: The 14 days are not complete
Google requires each of the 12 testers to have been opted in continuously for at least 14 days. Count from the day the last of your twelve qualifying testers joined, not from the day you created the track. Google does not state the exact moment the button appears, so check again the day after you finish counting.
| Tester joins on | Counts as 14 days on |
|---|---|
| Day 1 | Day 15 (after day 14 has finished) |
| Day 3 | Day 17 |
| Day 6 | Day 20 |
See how the 14-day requirement works for a worked example.
Cause 5: Testers opted out
Google says testers who opt out before 14 days do not count, and someone who opts out and back in must complete 14 consecutive days again. Ask everyone to confirm they are still opted in, replace people who left and track new start dates. Read what to do if testers leave and why testers are not counting.
Cause 6: You used the wrong track
The requirement is for a closed test. Internal testing is a different track and does not satisfy it, as explained in internal vs closed testing. If you only ran an open test, check closed vs open testing and Google's current requirement page.
Cause 7: You already applied
Google says the review usually takes seven days or less, though it can occasionally take longer, and the account owner receives an email when the review is complete. If you have already applied, wait for the email. Do not change your tester list during the review. See how long production access takes.
Cause 8: Your account may not need the test
If your account is not in the group Google's page describes, you may already be able to create a production release without applying. Open Production > Create new release. If it works, you are done: skip the application and go to how to publish your first app.
Cause 9: Account tasks are pending
Complete identity verification, payments profile tasks and the Android device verification in the Play Console mobile app. Then refresh the Dashboard. If something else is flagged, our developer verification guide lists the usual problems.
How do you check your tester count?
- Open your closed trackTesting > Closed testing > Manage track.
- Open the Testers tabCheck that your list or group is ticked and saved.
- Compare with your sheetCount testers who confirmed they installed the app and are still in.
- Check join datesFor each tester write the date they opted in.
- Check the 14-day markFind the latest join date among your twelve earliest, then add 14 days.
- Fix gaps immediatelyIf someone left, replace them today. A replacement needs 14 days of their own.
Good to know: Google requires at least 12 testers. A buffer of 15 to 20 protects you from drop-outs. See how many testers to recruit.
What happens after you apply?
Google's application has three parts: about your closed test, about your app, and about your production readiness. Answer with specifics: how you recruited testers, how engaged they were, what feedback you got and what you changed. If Google needs more testing, you keep the closed test running and apply again later; our guide to production access rejected explains how to improve your answers, and how to apply for production access walks through the form.
What can you do while you wait?
- Keep the closed test active and testers opted in.
- Prepare your production release and store listing.
- Finish the declarations: content rating, target audience, Data safety and app access.
- Plan your rollout. See staged rollout explained.
- Keep notes of tester feedback for the questionnaire.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
Sources
- Google Play Console Help: App testing requirements for new personal developer accounts
- Google Play Console Help: Set up an open, closed, or internal test
- Google Play Console Help: Create a Play Console developer account
Frequently asked questions
Where is the “Apply for production” button?
Google says you apply on the Dashboard in Play Console by clicking Apply for production. If you cannot see it, the requirements are usually not met yet, your account is not in the group that needs the test, or an application is already under review.
Why does Production show as disabled?
Google says Production and Pre-registration stay disabled for a personal account created after November 13, 2023 until the closed testing requirements are met, or while Google decides you need more testing.
Does the button appear exactly on day 14?
Google does not describe the exact moment. You need at least 12 testers opted in continuously for at least 14 days. Count 14 consecutive days from the day the last of your 12 qualifying testers joined, and check the Dashboard again.
My account is older than November 13, 2023. Why is there no button?
The testing requirement Google describes applies to personal accounts created after that date. Older accounts and organization accounts are not covered on Google's requirements page, so check your own Dashboard, which shows whether production is already available.
Does internal testing count?
No. The requirement is a closed test. Internal testing is a different track. See our guide to internal testing vs closed testing.
What if Google says I need more testing?
Google says you may have to keep your closed test running, for example because fewer than 12 testers were opted in or engagement was low. Keep the test active, replace testers who left and apply again when the requirements are met.
