"This Item Isn't Available in Your Country": Why Google Play Testers See This
A tester opens your opt-in link, taps "Become a tester," goes to the Play Store to install — and gets a flat "this item isn't available in your country" instead of an install button. The instinct is to blame the tester's account, region settings, or VPN. In the overwhelming majority of cases, the actual cause is sitting in your own Play Console.
The real cause: countries/regions on the testing track
Every closed testing track has its own countries/regions setting, separate from your app's main store availability. If that list is empty, too narrow, or simply doesn't include the country your tester's Play Store account is registered to, they'll see this exact error regardless of how correctly they followed the opt-in steps. It's on the same Testing page as your tester list — go to Play Console → your app → Testing → Closed testing → your track → Countries/regions and confirm it covers every country your testers are actually in.
Other things that produce the same error message
- The release is still under review. Before Google approves your first closed testing release, the opt-in flow can surface this error even with countries configured correctly — patience, not a settings change, fixes this one.
- Device or account country mismatch. A tester's phone set to one country while their Play Store account's payment/country profile is set to another can trigger it, independent of your track settings.
- App-level restrictions elsewhere in Play Console. Content rating gaps, an incomplete data safety form, or an app restricted from certain countries for policy reasons can produce a similar-looking availability error, separate from the testing track's own setting.
- Device compatibility exclusions. If your APK/AAB's manifest excludes certain hardware or Android versions and a tester's device falls outside that range, the Play Store can also present it as unavailable rather than incompatible.
How to actually diagnose it
- Check the track's countries/regions list first — this resolves it more often than everything else combined.
- Confirm the release itself shows as fully reviewed and live on the track, not pending.
- Ask the affected tester what country their Play Store account (not their SIM or IP) is set to, under Play Store → Settings → General → Account and device preferences.
- If everything above checks out for one tester specifically, suspect a device-compatibility exclusion in your manifest rather than a Play Console setting.
This exact error is one of the most common reasons a testing track stalls partway through recruitment — it's also one of the fastest to fix once you know where to look. See the full pre-flight checklist for the other configuration items worth checking at the same time.
See how it works — from $24 →FAQ
Why do my testers see "not available in your country" with a valid opt-in link?
Almost always because the closed testing track's countries/regions setting doesn't include the tester's country — check Play Console → Testing → Closed testing → your track → Countries/regions.
Does a VPN cause this error?
It can, but it's rarely the root cause for a legitimate tester using their normal device and account — the track's own country configuration is worth checking first.
Where exactly do I find the countries/regions setting in Play Console?
Play Console → your app → Testing → Closed testing → select your track → Countries/regions, right next to the tester list on the same page. It's a per-track setting, separate from your app's main store listing availability.