Closed Testing "App Not Available" for Google Group Testers: Fixes

Check these in order

1. 1Same Google account everywhere. The tester must be a member of the Google Group, open the opt-in link, and use the Play Store with that same account. On phones with several accounts, the Play Store often uses a different one.
2. 2Group membership first. If you use a Google Group, the tester must join the group before the opt-in link works for them.
3. 3Opt in through the link. The tester opens the web or Android opt-in link from Play Console, taps "Become a tester", then follows the link to the Play Store.
4. 4The release is rolled out. In Play Console → Testing → Closed testing, the release must be rolled out (not a draft, not halted). New tracks and releases can take several hours to become available.
5. 5Countries and devices. The closed track's country list and your app's device requirements still apply. A tester in a country not selected for the track, or on an unsupported device, will not see the app.

Is the right group on the track?

Open the closed track's Testers tab and confirm the Google Group address is listed and saved. If you use 12Tester Community, the group is get12testers@googlegroups.com. Adding it to a different track (for example internal testing) does not give access to the closed track.

Still not visible after all that?

• Ask the tester to clear the Play Store cache or try the web opt-in link on a computer while signed in to the right account.
• Wait a few hours after a new release: availability is not always instant.
• Check that the app is not restricted by age rating or content settings that exclude the tester.

Frequently asked questions