Skip to content

Google Play production accessNew Google Play accounts need 12 testers for 14 days before going live

If your personal Play Console account was created after November 13, 2023, the Production page stays locked until a closed test meets Google’s bar. Here’s the rule in Google’s words, how to run the test so it counts, and what the application asks, or have the build side handled at a fixed price.

Short answer

Finish your app setup, start a closed test and get at least 12 testers opted in. Keep them opted in for 14 days in a row, collect their feedback, then click Apply for production on the Play Console dashboard and answer the questions about your test. Google says its review usually takes seven days or less.

The route to production, in order

  1. 01

    Who the rule applies to

    “must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days” Google Play Console Help, App testing requirements

    Personal developer accounts created after November 13, 2023. Until the requirements are met, Play Console keeps Production and Pre-registration switched off. Accounts created on or before that date aren’t covered by this rule.

  2. 02

    Start a closed test once the app setup is done

    “You must run a closed test before applying to publish your app to production.” Google Play Console Help, App testing requirements

    Internal testing is optional and works before setup. The closed test needs the app setup finished. Upload your app bundle to the closed testing track, add testers by email list or Google Group, and send them the opt-in link. New apps must also meet Google Play’s target API level rule, so check that before the first upload.

  3. 03

    Keep 12 testers opted in for 14 days in a row

    “the 14 days must be consecutive to count toward the minimum requirement of 12 continuous opted-in testers” Google Play Console Help, App testing requirements, FAQ

    A tester who opts out before 14 days doesn’t count, and a tester who leaves and rejoins needs 14 days in a row. Google suggests recruiting from your own network and from the people the app is for, and telling testers to stay opted in. Our advice: invite more than 12, so one drop-out doesn’t leave you short.

  4. 04

    Collect feedback and ship fixes during the test

    “You must summarize your testing feedback when applying for production access.” Google Play Console Help, App testing requirements

    Testers can send private feedback through Google Play, which you read under Monitor and improve, Ratings and reviews, Testing feedback. Give them a channel of your own too, fix what they find and update the closed track while the test runs. The application asks what you changed.

  5. 05

    Apply for production and answer three parts

    “Review usually takes seven days or less, but can occasionally take longer.” Google Play Console Help, App testing requirements

    On the dashboard, click Apply for production. The form asks about your closed test, your app and its production readiness. If the app has a login, give the reviewers working test credentials. Google can ask for more testing, for example with fewer than 12 opted-in testers or low engagement.

Checked against the vendor’s docs on : Play Console Help: App testing requirements for new personal developer accounts; Play Console Help: Set up an open, closed or internal test; Play Console Help: Target API level requirements.

Rather hand it over?

Start with a paid consultation to agree the plan, then get a written quote with a fixed price.

Related: Target API 36 on Google Play · Android developer verification

Questions

More on this launch

Can you provide the 12 testers?

No. Google’s advice is to recruit testers who represent your app’s future users, and the application asks how easy recruiting was, how testers used the app and what feedback they gave. We think testers who actually use the app are the ones who can answer that, so we help with the app and the test setup, and the testers are yours.

Does this apply to my account?

Google’s rule is written for personal accounts created after November 13, 2023. If yours is one, Production stays switched off in Play Console until the closed test meets the rule and Google approves your application.

What if Google asks for more testing?

Google says it can, for example when fewer than 12 testers stayed opted in or engagement was low. Keep the closed test running, act on the feedback, ship an update and apply again.

Can you do it for me?

The build side, yes. The App Fix Ticket is for a problem in the app itself, not the testing rule: if Play rejects the build or it misses a requirement such as the target API level, the App Fix Ticket finds the cause and fixes it at a fixed price. For a whole launch, from the build to the store listing and the closed test setup, it starts with a paid consultation and a written quote. The testers and the application stay with you, since Google asks about your own test.

Something else?

Describe it and get a written quote

Describe the app and where it is in the launch. You get a written scope, a fixed price and a timeline; we reply by email, usually within one business day.