Seeing "0 opted in" after adding 12 testers is almost always one of five things, in order of how often it actually happens:
- Changes not sent to Google yet. Saving your tester list is not enough — Play Console requires a separate "Send changes to Google" step under Publishing overview. Testers cannot opt in until that's done.
- Countries restricted. If your track is scoped to specific countries and your testers aren't in them, they structurally cannot opt in — see why we recommend selecting all countries.
- The tester email list didn't actually save. A page refresh or a missed "Save" click on the Testers tab is common and easy to miss — re-check the list is really there before assuming the problem is elsewhere.
- The app isn't installable on a tester's Android version or device. If your app's minimum SDK excludes older devices, some testers genuinely can't install it.
- Play Console is still processing. After "Send changes to Google," propagation can take a few hours before opt-ins start appearing — this is the most common false alarm.
If you've checked all five and testers still show 0 opted in after several hours, open a support ticket — a specific stuck cohort is worth us looking at directly rather than guessing.