After the 14 days: production access review time and your first release
Updated November 2026
Your closed test has had at least 12 testers opted in for 14 days in a row. The Apply for production button is waiting. What happens next, and how long until your app is actually on Google Play? There are two separate waits: Google's review of your production access application, then the normal review of your first production release. This guide walks through both, using Google's Help Center for the official parts.
Before you click Apply
- At least 12 testers are opted in right now. Google requires this on the day you apply, not just at some point.
- Those testers have been opted in for at least 14 consecutive days.
- Testers actually used the app, and you can describe how.
- You have feedback to summarize and at least one change you made because of it.
- Your App content declarations, store listing and Policy status have no open issues.
Don't close the closed test or remove testers when you apply. If Google wants more testing, you'll need them.
Applying for production access
- Open Play Console and go to your app's Dashboard.
- Click Apply for production. Google shows this once the closed testing requirement is met.
- Answer the three parts: about your closed test (recruiting, engagement, feedback), about your app (audience, value, expected installs in year one) and about production readiness (what you changed and how you know it's ready).
- Click Apply. Google warns that answers are lost if you leave the page before Next or Apply, so draft them elsewhere first.
The guide on production access questions explains each question, and the free tool at https://testerexchange.com/tools/production-answers/ drafts answers from your real numbers.
How long the review takes
Google's Help Center says the review of a production access application usually takes seven days or less, but can occasionally take longer. The account owner gets an email when the review is complete.
Google doesn't publish a way to speed this up. Waiting a few extra days past a week is not unusual, and contacting support usually won't change the timing. Use the time to keep testing and fixing bugs; testers stay on your closed track.
The two possible outcomes
- Approved: you can access the Production page and publish your app on Google Play. Open testing also becomes available.
- More testing needed: Google says you may need to continue running your closed test, for example if you had fewer than 12 opted-in testers or not enough engagement. See the guide on what to do when production access is rejected.
Your first production release
Production access is not the same as being live. You still need to create a production release, and it goes through Google's normal app review like any other app. Google doesn't promise a fixed time for this review. New apps from new accounts often take longer than updates from established ones, so allow several days and plan your launch date with margin.
- Go to Test and release, then Production, then Create new release.
- Promote the build from your closed track, or upload a new .aab. Using the build your testers already ran is the safer choice.
- Write release notes and choose countries.
- Consider a staged rollout (for example 20% of users) so you can catch problems early.
- Send the changes for review in Publishing overview. If managed publishing is on, click Publish after approval to go live when you choose.
- Once approved and published, the app can take a little while to appear in Play Store search. Share the direct link in the meantime.
Full timeline from the first upload
- Closed track setup and first review: hours to a few days.
- Closed test: at least 14 days once 12 testers are opted in.
- Production access review: usually seven days or less, according to Google.
- First production release review: often a few days; can be longer.
- Total: plan on about four weeks from first closed-test upload to public listing, and more if anything needs fixing.
After launch
Google advises continuing to test your app before publishing production updates. Keep the closed track as a beta channel for your early testers, and consider open testing for a larger audience.
If you haven't reached day 14 yet, the biggest time saver is starting with enough testers. Tester Exchange sends real people on their own Android phones: $12.99 for 12, $14.99 for 15 or $22.99 for 25, paid once, or free if you test other developers' apps at https://testerexchange.com/earn. We recommend 15 so a dropout can't push you under 12 right before you apply.
Frequently asked questions
How long does Google take to approve production access?
Google says the review usually takes seven days or less, but can occasionally take longer.
Is my app live once production access is approved?
No. You still create a production release, which goes through normal app review before it's published.
Can testers leave once I've applied?
Keep them until you're approved. Google requires at least 12 opted-in testers when you apply, and you may need to continue the test.
Why is the Apply for production button missing?
It appears once you meet the requirement: at least 12 testers opted in continuously for 14 days. Check the Dashboard for your current count.
Can I speed up the review?
Google doesn't offer a way to. Make sure there are no policy or declaration issues so the review isn't held up.