“Not available in your country”: the country isn't on the track
Google Play blocks the test because the country of the tester's Play account isn't selected for the closed testing track. The developer adds it, ideally with every country, in the track's “Countries/regions” tab.
What you see
The test link or the Play Store says the app isn't available in your country, while testers elsewhere get it.
Why
A closed testing track is offered only in the countries the developer selects. Google goes by the country of the tester's Google Play account, not by where the tester is.
What to do
For the developer:
- In the Play Console, open the closed testing track, then its “Countries/regions” tab.
- Add every country and region, or at least the testers' countries, and save.
- If managed publishing is on, publish the change.
For the tester:
- Don't change your Play country to get around it: Google makes you wait at least 90 days between two changes.
- Check that your Peerbeta tester profile gives the country of your Google Play account.
- If it lasts, write to us from Help in the tester app: the fix is on the developer's side.
What Peerbeta does
Peerbeta invites testers whose Play country matches the countries declared for the test. When testers who can't get the app are in a country outside the track, the diagnosis tells the developer.
Was this helpful?
Your feedback shapes what we write next.
“Your device isn't compatible with this version”
Next →The tester's Play country isn't one of the track's countries