Stuck in Play Store Closed Testing? How to Fix It

Stuck in Play Store closed testing, with the console saying you have 12 testers while nobody is really testing your app? You need 12 testers opted in continuously for at least 14 days before Google lets you apply for production access.

The problem: the console says 12 testers, but nobody is testing

Your app is finished. You ran a closed test, applied for production access, and Google said no. Then a new closed test starts on its own, and the console still shows 12 testers opted in.

That is exactly what happened to one developer in June 2026. After his production access application was rejected, a third closed testing cycle started on its own on 24 June 2026. Play Console still counted 12 testers. The real number of testers, apart from himself, was zero. The app was installed on only 5 devices. He had deleted the Google Group holding his testers, hoping the count would reset. It did not. His support ticket was closed without a comment. He opened a forum thread on 27 June 2026.

Why it happens

Google's rule is the cause. For personal Play Console accounts created after 13 November 2023, you must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. Until you meet that, the Production and Pre-registration pages stay disabled. Review usually takes seven days or less.

Three things catch people out. First, being on the tester list is not enough on its own. Each tester has to open the opt-in link and accept, and then actually install the app and use it, or Google can still refuse you for low engagement. Second, the 14 days have to be continuous. A tester who opts out and back in starts a fresh 14 days. Third, meeting the numbers only lets you apply. It does not guarantee approval. Google can still refuse you if your testers were not engaged with the app during the test, and it can ask you to test for longer.

Business accounts do not have this requirement, but you cannot switch a personal account to a company account. You would need a whole new account. And in September 2026, one developer got the refusal email with the reason spelled out: testers were not engaged with the app during the closed test.

Stuck in Play Store closed testing: the minimum fix

Do these steps in order. The count only moves when real people opt in and stay.

1. Check whether the rule even applies to you. The 12-tester, 14-day rule applies to personal accounts created after 13 November 2023. Organisation accounts and older personal accounts are exempt.

2. Recruit 15 to 18 real testers as a buffer, even though Google's minimum is 12. With only 12, one dropout puts you back under the line, so the extra testers cover you if someone leaves. Ask friends, family, colleagues, or people like your real users. Each one must be a real person on a real device who will actually open the app.

3. Make opting in easy and check it worked. Send each tester the opt-in link, and ask them to open it, accept, and install the app. Then check both numbers: the opted-in count, which lets you apply for production access, and installed devices, which show whether testers installed the app. Installs alone do not prove they used it. In the June 2026 case, the console showed 12 opted in and only 5 installs. If installs are low, your test is not really running.

4. Give testers a short job to do. Tell them which features to try and how to report a bug. Google's own guidance says to ask testers to use as many features as possible. A tester who installs the app and never opens it does not help.

5. Collect the feedback and answer it. Read the Testing feedback page in Play Console, reply to testers, and fix the real bugs. Keep a short note of what feedback came in and what you changed. Google's page says you must summarize your testing feedback when you apply.

6. Apply only when the closed testing release is published and at least 12 testers have been opted in continuously for 14 days. Then apply and answer the three sections honestly: about your closed test, about your app, and about your production readiness, using your real test numbers and notes.

Do not delete your tester group and expect the count to reset. In the June 2026 case it did not work that way: the console kept counting 12 testers after the group was gone. Testing guides warn that emulators, bots, or duplicate accounts do not count as testers, so they will not move you toward the 12. And do not apply while your testers have not really used the app. That risks another refusal for low engagement.

When to get help instead

Get help if you have been refused again, if the tester count will not move, or if you need the production access answers written from your real test numbers. Get help too if your app still has crashes or broken screens. A clean test with real users and honest answers gives you the best chance of getting through.

If this is your app, contact me through https://israr-kundi.web.app