Skip to content

· 7 min read · Nadeera Silva

Mobile

Google Play 12 Testers for 14 Days: Get Production Access

New personal Play Console accounts need 12 testers opted in for 14 days. Here is what counts, what resets the clock and how to pass first time.

A grid of phones on a bright table with testers' hands reaching in from every side, standing for the 12 closed testers Google Play requires before production access

You built the app, uploaded the bundle and filled in every form in Play Console, but the Production page is locked and the dashboard says you must run a closed test first. Or worse, you waited two weeks, applied, and Google replied that your app needs more testing. This is the Google Play 12 testers for 14 days rule for new personal developer accounts. Below is exactly what the rule counts, the four mistakes that reset the clock, and the setup I use so a client's app gets production access on the first application.

Quick answer

If your Play Console personal account was created after 13 November 2023, you must run a closed test with at least 12 testers who have stayed opted in continuously for the 14 days before you apply for production access. Testers who opt out restart their own 14 days, and members of your internal test must leave it before they can join the closed test. Organization accounts, which need a D-U-N-S number, do not have this requirement.

What this means for your app or business

Plan for at least three weeks between "the app is ready" and "the app is live on Google Play": 14 days of closed testing, then a review that Google says usually takes seven days or less. If you promised a client or investor a launch date, this is the most common reason it slips.

There are two ways to reduce the risk. If you are a registered business, open an organization account (you need a free D-U-N-S number), which skips this testing rule. If you are an individual or a freelancer publishing under your own name, start the closed test as early as possible, even with an unfinished build, and recruit real testers from your users or network. If an agency publishes the app from its own organization account, the client does not own the listing, so decide whose account the app lives in before the first upload.

What exactly does the 12 testers for 14 days rule require?

RequirementDetailSource
Who it applies toPersonal accounts created after 13 November 2023Play Console Help
TrackClosed testing (internal testing does not count)Play Console Help
TestersAt least 12 opted in at the moment you applyPlay Console Help
DurationEach of those 12 opted in continuously for the preceding 14 daysPlay Console Help
ApplicationThree sections: your closed test, your app, production readinessPlay Console Help
Review timeUsually 7 days or lessPlay Console Help
Organization accountsNot subject to this rule; need a D-U-N-S numberPlay Console Help
Timeline of a closed test: at least 12 testers stay opted in from day 0 to day 14, then the developer applies for production and the app goes live
The 14 days count per tester and must be consecutive. Apply only when 12 of them have been in for the full 14.

Why was my production access application rejected?

Google's help page names two reasons for "continue testing": fewer than 12 opted-in testers, or insufficient tester engagement. In practice these come from four setup mistakes.

1. Testers joined the internal test instead

This is the one almost nobody spots. Google's testing tracks article says a user who opts in to your internal test is no longer eligible for an open or closed test. They must opt out of the internal test first, then opt in to the closed test. If you sent your friends the internal link first, they may be "testing" the wrong track.

2. Testers are on the list but never opted in

Adding an email address to the tester list does nothing on its own. Each person must open the opt-in link while signed in with that exact Google account and accept. The link can take several hours to work after the first closed release is published, so testers who tried immediately may have seen an error and given up.

3. Someone opted out and back in

Google is explicit: a tester who opts out and opts back in restarts their own 14 days. One tester who uninstalled and left the test on day 10 means you have 11 valid testers on day 14. I always recruit 15 to 20 so one or two drop-outs do not cost another two weeks.

4. Nobody actually used the app

The application asks whether testers used all features, whether usage matched what you expect in production, and what feedback you got and acted on. A closed test where 12 people installed once and never opened the app again gives you nothing to write, and Google can ask you to keep testing. Paid "tester exchange" services exist, as search suggestions show, but they add exactly this risk: Google asks about engagement, and strangers who install a dozen apps a day do not generate feedback you can describe.

Step-by-step: run a closed test that passes the first time

  1. Finish app setup. The closed testing track only opens after the app setup tasks on the dashboard are complete (content rating, data safety, target audience and so on).
  2. Build and upload. For Flutter, flutter build appbundle --release and upload the .aab to Test and release, Testing, Closed testing. Send the release for review.
  3. Create the tester list. Use an email list or a Google Group. For a CSV upload, Play Console wants one address per line, no commas, and no UTF-8 byte order mark. This is the quick check I run before uploading:
# testers.csv: one Gmail or Workspace address per line
sed -i '1s/^\xEF\xBB\xBF//' testers.csv        # strip an Excel UTF-8 BOM (GNU sed; on a Mac use gsed)
grep -c '@' testers.csv                           # expect 15 or more
grep -vE '^[^@,[:space:]]+@[^@,[:space:]]+$' testers.csv && echo "fix the lines above"
  1. Share the opt-in link from the Testers tab, plus a feedback email or form. Tell testers in plain words: "Stay opted in and keep the app installed for at least 14 days."
  2. Check that each tester is on the closed track, not internal. Anyone who joined internal testing earlier must leave it first.
  3. Give testers something to do. I send a short task list per week (sign up, make a test order, change a setting) and collect feedback in one place. Ship at least one update during the test based on that feedback.
  4. Apply on day 15 or later, from the dashboard. Answer the three sections with specifics: how many testers, what they tested, what you changed.

How do I verify I am ready to apply?

Before you click Apply, check that:

  • At least 12 testers opted in to the closed track 14 or more days ago, and none of them left since.
  • You shipped at least one update during the test (not a written rule, but it gives you real answers for the form).
  • You can describe the feedback you received and what you changed.
  • Your store listing, content rating, data safety form and target API level are all complete. My target API level guide covers the build side.
  • If login is required, you added working test credentials for reviewers.

How do I avoid this on the next app?

  • If you are a business, use an organization account from the start.
  • Keep a standing group of real testers (a Google Group works well) and reuse it across apps, so the next 14 days start the day you upload.
  • Start the closed test as soon as you have a stable build, not when the app is finished.
  • Watch for other 2026 Play changes too: the October 2026 Play policy update and the Android developer verification rules for 2027 both affect how and where you publish.

Frequently asked questions

What is the Google Play 12 testers requirement?

Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers who have been opted in continuously for the 14 days before applying for production access.

Does internal testing count toward the 12 testers?

No. The requirement is for a closed test, and Google says a user who opts in to your internal test is not eligible for a closed test until they opt out of the internal one.

What happens if a tester opts out during the 14 days?

That tester no longer counts. If they opt back in, their 14 days start again, so recruit a few more than 12.

Do organization accounts need 12 testers?

No. The rule applies to personal accounts created after 13 November 2023. Organization accounts need a D-U-N-S number to register.

How long does Google take to review a production access application?

Google says the review usually takes seven days or less, but it can take longer, and you get an email when it is done.

Why was my production access application rejected?

Google lists fewer than 12 opted-in testers and insufficient tester engagement as reasons to keep testing. Make sure testers used the app, gave feedback and that you acted on it.

Is it still 20 testers?

No. Google reduced the requirement from 20 to 12 testers on 11 December 2024. The 14 day period did not change.

Sources

  1. App testing requirements for new personal developer accounts (Play Console Help)
  2. Set up an open, closed, or internal test (Play Console Help)
  3. Choose a developer account type (Play Console Help)
  4. Ensuring high-quality apps on Google Play (December 11, 2024 update) (Android Developers Blog, 2024-12-11)
  5. Monthly newsletter January 2025: updated testing requirements (Google Play)
SharePost on XLinkedIn

Comments

Share a question or note about this article.

Loading comments…