Your Google Play closed test won't complete. Here's what's wrong.
You added testers, you waited, and the production button is still greyed out. Almost always it's one of these five things. Work down the list.
1. You have fewer than 12 testers opted in right now
The count is live: it reflects who's currently opted in, not everyone who ever joined. A few always drift away, so 12 exact becomes 9 fast. Fix: recruit 15–20 and keep a buffer.
2. Testers joined with the wrong email
A tester has to opt in with the exact Google account email you added — and be signed into that account on their device. Wrong email, or a different account on the phone, means they silently don't count.
3. Testers opted in but never installed
Opting in isn't installing. Some people tap the link, accept, and never download the build. Ask your testers to actually install and open it.
4. The 14 days haven't run continuously
The clock wants 14 uninterrupted days with 12 opted-in testers. If you dipped under 12 at any point, the requirement may not be satisfied yet. Let it run clean.
5. You've been churning the tester list
Removing and re-adding people mid-test disrupts the continuous-opt-in signal. Add extras up front instead of swapping testers in and out.
The real fix: reliable testers
Most of these problems come down to one thing — testers who opt in and then vanish. A reciprocal tester exchange fixes that at the source: everyone needs their own test to pass, so they have a reason to stay installed and engaged. New to the rule? Start with the closed-testing guide.
Frequently asked questions
Why does my tester count keep dropping below 12?
Because testers opt out or uninstall. The count tracks people currently opted in, not everyone who ever joined. Over-recruit to 15–20 so a few drop-outs don't pull you under the line.
Do testers have to use a specific email?
Yes. A tester has to join with the exact Google account email you added in Play Console, and that account must be signed in on the Android device they test with. A mismatch means they don't count.
Does removing and re-adding testers reset the 14 days?
It can disrupt the continuous-opt-in clock. Avoid churning your tester list mid-test — add extras up front instead of swapping people in and out.
I have 12 testers but the test still won't complete — why?
Usually the 14 continuous days aren't met yet, or some testers opted in but never actually installed and opened the app. Confirm all 12 are opted in AND have the app installed, then let the clock run uninterrupted.