If your Google Play developer account is a personal account created after 13 November 2023, the Production page in Play Console stays locked until you run a closed test with at least 12 testers who stay opted in for 14 days in a row. Then you fill in a three-part application, and Google reviews it, usually within seven days. The rules below come from Google's own help page, App testing requirements for new personal developer accounts, and the pages it links to.
The rule is simple to state and easy to fail on a detail: one tester who leaves on day 10, an opt-in link that never went live, or testers who joined and never opened the app.
The rule in one table
| Item | What Google requires |
|---|---|
| Who | Personal developer accounts created after 13 November 2023 |
| Which track | A closed test. Internal testing doesn't count, and open testing only opens after production access |
| How many testers | At least 12, opted in |
| How long | Opted in continuously for the 14 days before you apply |
| Then | "Apply for production" from the app's Dashboard: a three-part form |
| Review time | "Usually seven days or less", sometimes longer |
| Locked until approved | Production and pre-registration |
The path has six steps. Step 2 is easy to overlook: testers can't join until Google has published the closed release.
20 testers or 12?
Twelve. Google introduced the rule in November 2023 with 20 testers, in the Android Developers Blog post Ensuring high-quality apps on Google Play. An update to that same post, dated 11 December 2024, cut the number to 12 for personal accounts, after developers starting with small audiences told Google that 20 testers were hard to find. The 14 days did not change. Any guide or video that still says 20 predates that update.
Who has to run the test
Google's page names one group: personal developer accounts created after 13 November 2023. Personal accounts created before that date are outside it.
The page doesn't mention organization accounts. They are a different account type: Google's account type page says to choose an organization account when the account is for an organization or business, and that creating one requires a D-U-N-S number. If you are a registered business with a D-U-N-S number, that is the account type Google expects you to use anyway. If you are an individual, pick the personal account and plan for the test. Don't register as an organization just to avoid 14 days.
Does every new app need its own test? Google's page doesn't say. Its wording is per app ("run a closed test for their app"), so plan the 14 days for each new app until Play Console shows production as open for it.
What "opted in" and "14 continuous days" mean
Opted in means the tester opened your opt-in link while signed in with a Google account and accepted the invitation. Adding someone's email to your tester list does not opt them in. Testers need a Google Account or a Google Workspace account to join, per Set up an open, closed, or internal test.
Continuous is spelled out in Google's FAQ. Testers who opt in, test for fewer than 14 days and then opt out don't count. A tester who opts out and back in starts a new 14 days.
The 14 days are counted back from the day you apply. When you press Apply, at least 12 testers must each have been opted in for the whole preceding 14 days. A tester who joined late or rejoined counts only once their own streak reaches 14 days:
The practical consequence: recruit more than 12. If exactly 12 people join and one leaves on day 10, you need a replacement, and the replacement needs a full 14 days of their own.
Opting in only meets the count. The rule counts opted-in testers, but Google lists "insufficient tester engagement during the testing period" as a reason it may ask you to keep testing. Twelve names that never opened the app meet the count and can still fail the review.
Set up the closed test, step by step
- Finish app setup first. Google lists completed app setup as the requirement for closed testing. The setup tasks include the Data safety form; Google Play's Data safety form explained walks through each question.
- Create the closed track and a release. In Play Console, open the Closed testing page, create a release on the closed track and upload your app bundle (.aab).
- Add testers. Use an email list (up to 2,000 addresses per list) or a Google Group. With a group, testers join it themselves first and then opt in, so you don't collect emails one by one.
- Add a feedback channel. Give a feedback email or URL. It appears on the opt-in page testers see.
- Check countries. Google applies distribution country changes across all tracks, so make sure the countries your testers live in are included.
- Send the release for review and wait. The opt-in link only shows when the release status is Published, not Draft or Pending publication. After the first publish, the link can take several hours to become available.
- Share the link. Testers can't find a closed test by searching Google Play. The opt-in link has this format, with your app's package name at the end:
https://play.google.com/apps/testing/com.yourcompany.yourappOne more detail for paid apps: testers in closed and open tests have to buy a paid app like anyone else.
The invite message
Google's own advice is to tell testers they must stay opted in for at least 14 days. Put that in the first message, together with the link and what to try. A template you can adapt:
Hi [name], I'm about to publish [App name] on Google Play and I need
testers for two weeks.
1. Open this link on your Android phone, signed in with your Google account:
https://play.google.com/apps/testing/[package name]
2. Accept the invitation, then install the app from the Play Store link on that page.
3. Please stay in the test for at least 14 days. Leaving and rejoining
restarts your 14 days.
4. Use it a few times: [2 or 3 things to try]. Send anything that breaks
or confuses you to [email or group chat].
Thank you!NasrTech publishes a number of its own apps on Google Play, and Nasr App Maker ships this step ready-made: the publishing kit includes an "invite your testers" message with the opt-in link already filled in for your package name, and the paid kit gives that text in both English and Arabic.
What to do during the 14 days
Google's best-practice list for closed testing asks for a handful of things that also become your answers on the application form.
- Give testers a short task list. Google recommends clear instructions and encouraging testers to use as many features as possible. "Try the app" gets you an install. "Sign up, add an item, share it" gets you feedback.
- Keep every piece of feedback in one place. Testers can send private feedback through Google Play, and you can read it in Play Console under Testing feedback. It never touches your public rating. Note what people said, because the form asks you to summarize it.
- Ship at least one update to the closed track. Google advises updating the app in closed testing before you release to production. Testers get the new version as an update through Google Play.
- Run the pre-launch report. Google points to it as a way to catch crashes and other problems early.
- Watch your opted-in count. Replace anyone who leaves early, and remember that a replacement starts at day 1.
- Keep a group chat. Google suggests a messaging group for testers. It is also the fastest way to remind people not to leave.
The production access application
When at least 12 testers have 14 continuous days, open the Dashboard and choose Apply for production. The form has three parts. If you click Discard, or leave a page before clicking Next or Apply, your answers are lost, so draft them in a document first.
| Part | What Google asks | What a strong answer has |
|---|---|---|
| 1. About your closed test | How easy it was to recruit testers; whether they used all the app's features; whether their usage matched what you expect in production, and how it differed; a summary of the feedback and how you collected it | Who your testers were, what you asked them to try, two or three concrete pieces of feedback |
| 2. About your app or game | Your target audience, as precisely as you can; the app's value (or what makes the game unique); your estimated installs in the first year | A specific audience ("owners of small gyms who already have a booking website"), not "everyone" |
| 3. About your production readiness | What you changed because of the closed test; how you decided the app was ready | The fixes you shipped, with version numbers, and the checks you ran |
Google states that the Part 2 answers don't affect your app's visibility, your access to Play Console features or your eligibility for developer programs. Answer them honestly.
Why Google says no
Google names two reasons it may ask you to keep testing instead of granting access:
- Fewer than 12 opted-in testers.
- Insufficient tester engagement during the testing period.
It also says the review "is not a troubleshooting step". An app that breaks policy leads to a rejection, a delay or a longer appeal. Before you apply, Google asks you to confirm that the app's content and monetization follow Google Play policies, that the target age group and content rating are accurate, that the app is stable with no crashes, broken features or missing screens, and that working test credentials are in Play Console if the app needs a login.
The checklist below combines those points with the test itself:
Tester exchange groups and paid testers
Two shortcuts come up again and again in developer forums.
Tester exchange groups. Developers join a group, opt in to each other's tests and stay for 14 days. Nothing in Google's help page forbids testing each other's apps. The risk is the second rejection reason: someone who joins many tests at the same time has little reason to use yours, and you end up with nothing real to write in Part 1. If you use an exchange, treat it as extra headcount on top of people who actually fit your audience, and ask exchange testers to try specific features and report back.
Paid tester services. Sellers offer "12 testers for 14 days" as a package. Google hasn't published a rule that names these services. Its User Ratings, Reviews, and Installs policy does prohibit inflating install counts by illegitimate means, and the application asks you to describe how you recruited testers and what they told you. A bought batch of opt-ins with no feedback leaves you with an application you can't answer honestly. Your developer account carries every app you will ever publish, so it is not worth risking it to save two weeks.
Google's own suggestion for recruitment is your personal and professional network, communities and social media, aiming for a group that looks like your intended users. For a business app, that often means your existing customers and staff.
If your app is a website turned into an app
A closed test is a cheap place to find out whether a wrapped website feels like an app. Testers on real phones will notice what you don't: a page that needs the browser's back button, a login that loops, a blank screen with no signal. Google's minimum functionality policy also rejects apps with only limited functionality and content, such as static text-only apps, and the reviewer sees the same app your testers do.
If you are starting from a site, turn your website into an Android app with Nasr App Maker: the live preview and 3 test APKs a month are free, so you can hand a test build to a few people before you even open Play Console. The paid plans add the signed Google Play bundle (.aab) with your own upload key, a hosted privacy page, and drafts for the listing and the Data safety form, plus the tester invite described above.
After Google approves
Approval unlocks the Production page and open testing. The listing needs its images before you can roll out:
- A 512 × 512 icon. The Google Play icon resizer produces the exact file from any image.
- A 1024 × 500 feature graphic. The feature graphic resizer crops and exports it.
- Phone screenshots in sizes Play accepts. The Google Play screenshot size guide lists them.
You can prepare all three during the 14 days, so the production release is ready the day the email arrives.
Frequently asked questions
Is it 12 or 20 testers in 2026?
- Google lowered the requirement from 20 to 12 testers for personal accounts on 11 December 2024. The 14-day period stayed the same.
Do organization accounts need 12 testers?
Google's requirement page covers personal accounts created after 13 November 2023 and doesn't mention organization accounts. Organization accounts are meant for businesses and need a D-U-N-S number to create.
What happens if a tester leaves on day 10?
They stop counting. If they rejoin, their 14 days start again. If that drops you below 12, add someone new, who also needs 14 continuous days before you apply.
Do testers have to install and use the app?
The count is based on opted-in testers. Google also lists insufficient tester engagement as a reason to keep testing, and the form asks whether testers used all the features. In practice, ask every tester to install the app and use it.
Can I apply on day 14 exactly?
The 14 days must be complete and continuous for each tester at the moment you apply. Applying the day after your twelfth tester's 14th day is the safe reading.
How long does the production access review take?
Google says it usually takes seven days or less but can take longer. The account owner gets an email when it's done.
Can I push updates during the closed test?
Yes, and Google recommends it. Testers get the new version as an update through Google Play. Describing what you changed is part 3 of the application.
The short version
Recruit 15 or more real people who fit your audience, wait until the closed release shows Published, send them one clear invite, keep all of them in for 14 full days, ship a fix based on what they tell you, and write the application from your notes. The 14 days can't be shortened. A tester who leaves, and a replacement who starts at day 1, can only make them longer.