Getting from a new personal developer account to a live production app takes longer than 14 days. Before the clock starts, your closed track has to be reviewed and published, and after the 14 days your production access application has its own review. Plan for several weeks in total and you won't be caught out.
This article walks through the stages in order, with what happens at each one and what usually causes delays. The requirement itself applies to personal accounts created after November 13, 2023.
Before day 0: account and app setup
Two things have to be finished before you can even create a closed test.
Your account. New personal accounts go through identity verification, and since early 2024 they also have to "verify that they have access to a real Android mobile device using the Play Console mobile app". That task appears on the Home page. If either is stuck, everything else waits.
Your app setup. Google says closed testing "requires completing app setup first". In practice that means the declarations under Policy and programs > App content, including the Data safety form, which is required for closed tracks even if your app collects no data. You also need a signed app bundle that meets the current target API level rule.
Our checklist of 10 things to have ready before day 1 covers this stage in detail.
Day 0: create the track and send it for review
On day 0 you set up the closed track:
- Choose the countries and regions for the track. Testers in a country you didn't select likely can't get the test.
- Add your testers by email list or Google Group.
- Upload your app bundle to a new release on the track.
- Open Publishing overview and click Send for review.
Step 4 is the one people forget. Until you send the changes, they sit under "Changes not yet sent for review" and nothing reaches Google. The full walkthrough is in how to create a closed testing track, and the upload itself is covered in uploading your first app bundle.
Days 0 to 7 (sometimes longer): track review
Google reviews the closed release before testers can use it. According to Google's managed publishing documentation, reviews can take "a few hours or up to seven days (or longer in exceptional cases)", and Google recommends leaving a buffer of at least a week. New developer accounts may see longer reviews.
This waiting time doesn't count toward your 14 days. Nobody can opt in yet.
When the track is published: share the link
Once the release is approved, the track status becomes "Published". Google says "the opt-in link displays only when an app status is 'Published'", and after the first publish "the test link can take several hours to become available to testers."
Copy the link from the track's Testers tab and send it to your testers. Each tester opens it, reads the explanation of tester responsibilities and accepts. How testers join a closed test shows the flow from their side.
Day 1: the clock starts per tester
There's no single start button for the 14 days. Each tester's streak starts when they opt in. What matters is that "at least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days."
So the practical start date is the day your 12th tester opts in. If eight people join on Monday and the last four join on Thursday, count from Thursday. Recruiting a few more than 12 gives you a buffer if someone leaves. What counts as an opted-in tester explains the rule with examples.
Days 1 to 7: first week of testing
The first week is where you learn the most:
- Make sure every tester could install the app and log in, if your app needs a login.
- Watch for crashes and broken screens.
- Collect feedback in one place, and note what you plan to change.
Keeping the app installed and using it regularly is strongly advised. Google may ask for more testing because of "insufficient tester engagement during the testing period".
Days 8 to 14: second week
Attention tends to drop in the second week. A good way to keep testers active is to ship an update that fixes what they reported. It isn't an official requirement, but Google recommends you "continue running closed tests while resolving user-reported issues and bugs", and the application form asks what you changed based on the test.
Google measures the 14 days on testers' opt-in, and nothing in its documentation says a new build on the same track restarts them. Removing testers or countries from the track is a different matter: it may cut testers off, so leave the tester setup alone.
Day 15: apply for production access
When at least 12 testers have 14 continuous days behind them, open the Dashboard and click Apply for production. The form has three parts: your closed test, your app, and your production readiness. You must summarize your testing feedback, which you'll find under Monitor and improve > Ratings and reviews > Testing feedback.
We recommend applying on day 15 rather than the exact day 14, so every tester clearly has a full 14 days. Our production access guide has example answers for each question.
After you apply: the review
Google says "review usually takes seven days or less, but can occasionally take longer." The account owner gets an email when it's done. Keep your closed test running while you wait.
There are two possible outcomes:
- Approved. The Production page and Open testing are unlocked, and you can create your first production release. That release also goes through review.
- More testing required. Google lists "fewer than 12 opted-in testers or insufficient tester engagement" as reasons. Continue testing, fix the cause and reapply when you're ready. Google doesn't publish a fixed waiting period.
The timeline at a glance
| Stage | What you do | How long |
|---|---|---|
| Setup | Verification, App content, app bundle | Depends on you |
| Day 0 | Create track, Send for review | One session |
| Track review | Wait | A few hours to 7 days, sometimes longer |
| Published | Share opt-in link | Link can take several hours |
| Days 1 to 14 | Test, collect feedback, update | 14 consecutive days |
| Day 15 | Apply for production | One session |
| Application review | Wait, keep testing | Usually 7 days or less |
Key takeaways
- The 14 days start when your 12th tester opts in, not when you create the track.
- Track review and application review add time on both ends.
- Never remove testers during the test or while your application is under review.
If you don't have 12 people ready for day 1, GoPlayTester provides 12+ real testers in Indonesia who stay opted in for the full 14 days. Our setup guide shows how to add the tester group. Google makes the final decision on your application.
