Frequently asked questions

Google Play closed testing questions, answered.

Learn how tester engagement, feedback, production access, and common setup issues work with 12Testers.

What does tester engagement mean during a closed test?

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.

How do you make sure testers use my app?

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.

Do you help with the production access questionnaire?

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.

What happens if my app gets rejected?

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.

How do you reduce insufficient-testing problems?

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.

What is 12Testers?

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.

Why does my app appear as Not Accessible?

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.

What if my app requires login credentials?

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.

Are TWA or browser-based apps supported?

They can be tested, but the testing plan should cover the actual app experience and any native integration. Production access is not guaranteed for any architecture, and the app must still meet Google Play policies.

What should I check if testers are blocked by country restrictions?

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.