Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Google Play will not let me publish: it asks for 12 testers

Short answer

For newer personal developer accounts, Google requires a closed test with at least 12 testers opted in continuously for 14 days before you can apply for production access. Google reviews the application, and if it wants more testing you keep the closed test running. Check your account type first, then recruit real testers who actually open the app.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The Play Console says I must run a closed test before I can publish my app.
  • I do not have 12 people to test my app and I do not know who to ask.
  • I applied for production access and was told to keep testing.
  • My testers joined, but some left and the count dropped.
  • I thought my app was finished and now it is stuck before the store.

Why does this happen?

  1. A newer personal account has to prove the app is tested

    Google's help page says the closed test requirement applies to personal developer accounts created after a cutoff date it states. 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.

  2. A tester who leaves resets their own clock

    Google states that a tester who opts out and back in needs 14 consecutive days again to count. A group that looks big enough on day one can fall short on day 14.

  3. Google can ask for more testing

    After you apply, Google reviews the application. Its page gives two reasons why you may need to continue the closed test: fewer than 12 opted-in testers, or too little tester engagement during the testing period.

  4. The application form is part of the test

    You apply from the Dashboard with three sections: about your closed test, about your app, and about your production readiness. Google says changes in a section are not saved if you leave it without clicking Next or Apply.

  5. An organisation account works differently

    Google's article covers personal accounts. If your business registered an organisation account, check the Console first, because this rule may not be what is blocking you.

What can I do about it today?

  1. Confirm the type of your accountOpen the Play Console and check whether the account is personal or an organisation. The requirement in Google's article is written for personal accounts.
  2. Read what the Dashboard actually asksThe Dashboard shows the steps Google expects for your app. Screenshot them, so the next person who helps you sees exactly what is outstanding.
  3. Ask real people to joinInvite staff, friends and customers who will really install the app and open it. Ask them to stay opted in, because a tester who leaves stops counting toward the 14 days.
  4. Give testers something to doGoogle looks at tester engagement, so ask each tester to use the app in a normal way during the period, and to send you what confuses them.
  5. Apply only when the counts are metCheck that 12 testers have stayed opted in for 14 days before you click Apply for production, then fill in all three sections and click Apply at the end.
  6. Do not create a second account to skip the ruleA second or borrowed account can put the first one at risk. Keep to one account in your own business name.

When should I bring someone in?

  • You applied, were asked to keep testing, and do not know what Google wants to see.
  • Your app is not ready for real testers, or you cannot gather 12 people who would use it.
  • You need the closed test, the questionnaire answers and the first release handled together.

How do I handle it?

  1. Check the account and the DashboardI read what your Console asks for and write down what is missing, so nothing is guessed.
  2. Prepare a build worth testingI put a signed release on the closed track, with a short note for testers on what to try.
  3. Run the test period with youI help you plan who joins, how to keep them opted in and how to collect their feedback and fix what they find.
  4. Write the production application honestlyThe three sections are answered from what actually happened in the test, not from a template.
  5. Make the first release routineOnce access is approved, the production release uses the same signed build process, so the next update is a normal step.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Do I always need 12 testers?

Not every account. Google's article describes the requirement for personal developer accounts created after a date it states. Check your own Console to see what applies to you.

How long does Google take to answer my application?

Google's page says it typically reviews applications within seven days, though it can take longer. The decision is Google's, so I cannot promise an outcome.

What if testers drop out?

Google says testers must be opted in continuously for 14 days, and a tester who opts out and back in needs 14 consecutive days again. Recruit more than 12 so one departure does not reset your plan.

Can you be my testers?

No. Testers should be real users of your kind of app. I can run the process around them and fix what they report.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.