Finish closed testing and apply for production access

Complete the 12-tester requirement, keep useful feedback, and apply when Play Console says your app is eligible.

By The Draftbit team · Updated
Sources checked

This guide is for Apps on personal Google Play developer accounts created after 13 November 2023.

You’re ready to launch, but Play Console wants a closed test first. If this requirement applies to your account, finishing the test lets you apply for production access. Google still reviews that application, and there’s a separate app review before publication.

Check the account type and creation date first. If this requirement applies to you, prepare a usable test release, recruit testers you can rely on, and decide how you’ll collect their feedback.

Run the closed test

Publish the build to a closed testing track and invite eligible testers through its opt-in flow. Keep enough people opted in for the full period shown in the requirement above. If someone leaves and rejoins, their earlier time doesn’t count as one continuous opt-in period.

We recommend choosing testers you can rely on to use the app’s main flows and report problems. Keep a record of what they found, what you fixed, and what still needs testing.

Google doesn’t publish a daily app-opening quota for this requirement. Keep the report tied to what actually happened, with real activity records. Paid opt-ins alone don’t demonstrate a useful test.

Apply when Play Console says you’re eligible

Open the production-access task and check your eligibility. The application asks about recruitment, tester engagement, feedback, improvements, the intended audience, and whether the app is ready for production. Use your testing record to answer.

Google says applications are usually reviewed within 7 days or less, though they can take longer. Once Play Console grants production access, prepare the production release and complete its separate app-review steps.

If the counter or application isn’t moving forward

Check that you’re using the closed track and that enough eligible testers stayed opted in continuously. An internal test doesn’t replace this requirement.

If Google asks for more testing, use its feedback to improve participation, test coverage, or the app itself. Reapply when you’re eligible.

If the application isn’t available, use the closed-test counter checks. If Google has already denied access, use the feedback-and-fixes worksheet to prepare your next test and application.

Messages this guide can help with

12 testers; 14 days; 20 testers; production access denied; apply for production

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit a Google Play release with working review access