During a closed test, testers usually can't find your app by searching Google Play. They reach it through the opt-in link, and then through the app's Play Store page on the account that opted in. If a tester has opted in and still sees nothing, the cause is almost always the account, the country or the device, not a bug in your app.
This article is about the step after opting in. If the opt-in link itself is failing, start with opt-in link not working? 8 fixes.
Why search isn't the way in
A closed test is a private release. It's meant for the people on your tester list, not the general public. An app that has never been released to production has no public listing for search to show. So it's best to assume that typing the app's name into Play Store search won't find it, even for testers who have opted in.
What testers should do instead:
- Open the opt-in link you shared and accept the invitation.
- On the confirmation page, follow the link to download the app on Google Play.
- Or open the app's Play Store URL directly (the
play.google.com/store/apps/details?id=...link with your package name), signed in with the same account.
If you are setting up the links for the first time, where to find the opt-in link explains which link is which.
Cause 1: The tester never finished opting in
Opening the link isn't the same as joining. Google's help says testers "receive an explanation of tester responsibilities and a link to opt in. Each tester needs to opt in using the link." A tester who stops at the explanation page isn't a tester yet, and the app page won't offer them the test version. Ask them to open the link again and check whether it now says they are a tester. See how testers join your closed test for what each screen looks like.
Cause 2: The Play Store app uses a different account
This is the most common cause. The tester opted in on a laptop browser with one Gmail account, but the Play Store app on their phone uses another. The Play Store shows the app based on the account that's active in the Play Store app.
Fix: in the Play Store app, tap the profile picture, switch to the account that opted in, then open the app link again. If the account they opted in with isn't on the phone at all, they need to add it, or opt in again with the account the phone uses (if that account is on your tester list).
Cause 3: Their country isn't on the closed track
Closed testing tracks have their own country and region settings, which are synced with production by default. If the tester's country isn't selected for the track, it's likely the app won't be offered to them even after opting in. Check Testing > Closed testing > Manage track > Countries/regions. Our article on countries and regions for a closed track explains how to edit this.
Cause 4: The device isn't compatible
If the tester can see the page but there's no install button, or they see a message that the app isn't available for their device, the cause is usually compatibility. The device may run an Android version below your minSdk, lack a hardware feature your manifest requires, or be excluded in your device catalog. Check your app's minimum SDK and required features against the tester's phone.
Cause 5: The release just went live
After you publish a closed test for the first time, Google notes that "the test link can take several hours to become available to testers." Later updates can also take a little while to reach every tester after approval, but Google only documents the several-hour delay for the first publish. If you only just published, ask testers to wait a few hours before they report a problem.
Cause 6: The app is paid
For closed and open testing, Google's help says testers "must purchase paid apps". Only internal testers get paid apps for free. If your app is paid, testers will see a price instead of an install button. Many developers run the closed test with a free version of the app instead.
A message you can send to testers
Clear instructions prevent most of these problems. You can adapt this:
- Open this link in Chrome while signed in with [the Gmail address you gave me]: [opt-in link]
- Tap the button to become a tester and wait for the confirmation.
- Tap the "download it on Google Play" link on that page. Don't search for the app by name.
- Make sure the Play Store app on your phone uses the same Gmail account.
- Keep the app installed and open it regularly during the test.
When to worry
If several testers in the same country and on the same account setup all fail, look at your track setup: the countries, the tester list, and whether the release is fully published in Publishing overview. If only one tester has trouble, it's almost always their account or device.
Key takeaways
- Testers reach the app through the opt-in link and the direct Play Store link, not through search.
- The Play Store app must use the same account that opted in.
- The country, device compatibility and pricing can each hide the app.
- Every tester who can't install is a tester whose 14 days may be at risk.
When you use GoPlayTester, you send us both links (the Android link and the web testing link), and we check them before testing starts. That's covered in our setup guide. If you still need testers, you can order a 14-day test.
