Google Play closed testing questions, answered.

Google asks developers to describe how testers used the app, what feedback they provided, and what changed as a result. Testers should exercise the app's important workflows and report useful findings instead of only opting in.

We give testers clear instructions to open the app, work through its main features, and report bugs or confusing behavior during the 14-day test. The resulting feedback supports an accurate production-access application.

Yes. Eligible plans include guidance for describing your real testing process, tester feedback, changes made, and production readiness. The final answers must always reflect what actually happened in your test.

If Google requests more testing because of the testing activity covered by your plan, we provide the retest described in our refund policy. App quality, policy compliance, and the accuracy of your production-access answers remain the developer's responsibility.

We coordinate real testers, keep the tester count above the required minimum, provide a practical test plan, and collect feedback throughout the testing period. Google makes the final production-access decision.

12Testers is a managed Android closed-testing service. We help developers coordinate real testers for the 14-day Google Play requirement and prepare evidence-based production-access answers.

Common causes include missing tester access, a release that is still under review or not fully published, country restrictions, a mismatched Google account, or an incorrect package name.

Provide dedicated test credentials through the private support channel so testers can reach the app's important workflows. Do not place passwords or other secrets in public feedback.

No. We do not accept Trusted Web Activity (TWA) or other browser-based apps for our closed-testing service. Please contact support before ordering if you are unsure whether your app qualifies.

Our dashboard shows the tester count included in your plan while testing is in progress; it does not read live opt-ins from Google Play. Google Play Console counts testers who have opted in to your closed test, and its figures may take time to update. The apps-list users/downloads and Statistics numbers measure different things, so they are not a reliable opt-in count. Our professional team includes 15+ testers who open and use assigned apps daily, but only Google can determine which opt-ins qualify toward your production-access requirement.

In Google Play Console, select your app and open Dashboard > Apply for production. Check the closed-testing checklist for the number of opted-in testers and their consecutive days. For affected personal developer accounts, Google requires at least 12 testers opted in continuously for 14 days before you can apply for production access. Do not use the apps-list or Statistics install figures to judge that requirement.

First confirm that your closed-testing release is published, the correct tester list or group is assigned to the track, and the opt-in link works for testers in the enabled countries. Give Play Console time to update, then contact 12Testers support with a screenshot of the Dashboard checklist if it still shows fewer than 12. We will review tester access and opt-ins with you. Wait until Google's checklist confirms the required count and consecutive days before applying for production access.

Make sure the closed-testing release is available in every country where an assigned tester is located. Your support instructions list the current tester regions to enable in Play Console.