Fix "app not available" for Google Play closed testers
Updated November 2026
Your testers open the link and Google Play says the app isn't available, can't be found, or isn't compatible. Every day this lasts is a day your 14-day clock isn't running. Almost always the cause is one of a handful of setup problems, and you can check them all in about ten minutes. Work through this list in order.
Quick checklist
- Is the release on the closed track Published, not In review or Draft?
- Is the tester's email (or your Google Group) on that same closed track?
- Did the tester open the opt-in link and tap to become a tester?
- Is the tester signed in to Google Play with that same Google Account?
- Is the tester's country selected for the app?
- Does the tester's phone meet your minimum Android version and device requirements?
- Has it been a few hours since the first publish?
- Is the tester also opted into your internal test?
1. The track isn't published yet
Google says the opt-in link displays only when the app status is Published. If your first closed release is still in review, or saved but never sent for review, testers will see nothing useful.
Open Publishing overview. If there are changes waiting to be sent, send them. If managed publishing is on, approved changes wait until you click Publish. Also check the Inbox and Policy status pages for rejections.
2. It was published minutes ago
Google notes that after the first publish the test link can take several hours to become available, and later changes can also take several hours. If everything else is right, wait half a day before changing anything. Changing settings repeatedly can trigger new reviews and add delay.
3. The tester isn't on the track
Being invited is not the same as being on the track. Open Test and release, then Testing, then Closed testing, then Manage track, then Testers. Make sure the email list with the tester's address is ticked for this track and saved, or that your Google Group address is entered under Google Groups.
With a Google Group, the tester also has to be a member of the group before opting in. Google says only members of the specified groups can join the test. If you use Tester Exchange, the group to add is testerexchange-testers@googlegroups.com, and we add our testers to it.
4. Wrong Google Account on the phone
This is the most common cause with friends and family. The tester gave you their work email, or the phone has two Google Accounts and the Play Store is using the other one.
Ask the tester to open the Play Store, tap their profile picture and check which account is active. The opt-in link must be opened while signed in to the account on your list, in the same browser profile. Then they install from the Play Store on the phone with that account. If needed, add their other address to your list too.
5. The tester never opted in
Each tester must open the opt-in link and accept, one by one. Sending them the Play Store link alone isn't enough. After they accept, Google shows a link to download the app from Google Play. Testers can't find a closed test by searching the Play Store.
6. Country or device not supported
If the tester's country isn't in your Countries / regions list, the app won't be available to them. Add the country; Google says country changes apply across all tracks.
"Your device isn't compatible" usually means your minimum SDK, required features (for example a camera or specific CPU architecture) or device exclusions rule out that phone. Check the Device catalog in Play Console. Games built only for 64-bit ARM, or with high minimum Android versions, often hit this.
7. They're in your internal test
Google says users who opt into internal testing aren't eligible for open and closed testing. If a tester joined your internal test earlier, they must leave it first (open the internal opt-in link and leave the program), then opt into the closed test.
8. Play Store is showing an old state
If all of the above is right, ask the tester to close the Play Store, clear its cache in Android Settings, and try again. Opening the opt-in link in Chrome on the phone rather than inside another app's built-in browser also helps.
Protect your 14 days while you fix it
The requirement counts 12 testers opted in continuously for 14 days, so testers who can't get in don't help. Recruit a few extra (15 is a good target) so one stuck tester doesn't delay the whole test. Tester Exchange replaces testers who stop, and its setup screen tells you exactly which Play Console step to take if our testers can't install your app.
Frequently asked questions
Why does the Play Store say "item not found"?
Usually the release isn't published yet, the tester is signed in with a different Google Account, or they aren't on the track's email list or Google Group.
How long after publishing can testers install?
Google says the first test link can take several hours to become available.
Do testers who can't install count toward 12?
Only opted-in testers count. Someone who never managed to opt in doesn't help your 14 days.
Can testers find my app by searching Google Play?
No. Closed tests don't appear in search. Share the opt-in link or the Play Store link.
Do I need to republish after adding testers?
Adding emails to a list or members to a Google Group doesn't need a new release. Save the Testers tab changes and send them if Publishing overview asks.