"Not Available in Your Country" During a Google Play Closed Test: What I Check

A tester messaged me on day two of a closed test: the opt-in link worked, they tapped "Become a tester", and then the Play Store page said the app wasn't available in their country. Everyone else on the list could install it.

The cause wasn't the build or the tester list. It was the countries setting on the closed track itself. Here's how I track this one down now, because a tester who can't install is a tester who probably won't stay opted in long enough to help with the 12 testers for 14 days requirement.

Closed tracks have their own country list

This is the part that catches people. Each testing track in Play Console has its own countries/regions setting, separate from what you plan for production.

Open Testing > Closed testing, pick the track your testers joined, and look at the Countries / regions tab. If you created the track quickly and only ticked your own country, anyone whose Play Store is set to another country can opt in through the link but can't install. Add the countries your testers are actually in, save, and give it a little time before asking them to retry.

The tester's Play Store country is not where they're sitting

Google Play decides a user's country from their Play account, mostly from their payments profile, not from their current location or VPN. A tester who moved, or set up their account while travelling, can show up as a different country than you expect.

I ask the tester to open the Play Store, go to Settings > General > Account and device preferences and read the country listed there. That one answer usually settles it. I don't ask testers to change their country, because Google limits how often that can be done and it affects their whole account.

Device compatibility can look like a country problem

Sometimes the message is really "your device isn't compatible", and testers report it loosely as "not available". Before touching countries, I check:

• minSdk against the tester's Android version
• required hardware features in the manifest (camera, NFC, telephony) that a tablet or older phone may lack
• the Device catalog in Play Console, in case a device was excluded

Check the release actually reached the track

If the latest closed release is still in review or was never rolled out to that track, testers can see odd Play Store states. I confirm the release shows as available on the same closed track the opt-in link belongs to before I start adding countries.

Re-test with the opt-in link, not a search

Closed test apps usually don't show up in Play Store search. After fixing the countries list, I ask the tester to open the opt-in link again on the phone signed in with the invited Google account, then tap through to the store listing from there.

What I keep in mind about the 14 days

Fixing availability doesn't backfill the days a tester couldn't install. If someone joins late, I count their 14 continuous days from when they're actually opted in and able to use the app, and I plan the test with a couple of extra testers and a couple of spare days so one country mix-up doesn't push the whole timeline.

If you want to sanity-check the setup before inviting anyone, I keep a short run-through of how a closed test is put together on the Google Play closed testing guide. Production access is still Google's call after the test, so none of this is a shortcut. It just removes one avoidable reason testers drop off in the first week.