Closed Testers Can't Install Your App? How to Fix Country Availability in Google Play Console

Disclosure: 12Testers14Day publishes this article and sells Google Play closed-testing help.

A tester accepts your closed-testing invite, opens the Play Store link, and finds no Install button. Sometimes Play tells them the app isn't available in their country. You never chose to block that country, so what happened?

Usually it's one of three things: the tester's Play country isn't in your closed track's country list, the track is quietly copying your production country settings, or the change you made hasn't reached testers yet. This guide explains how Google decides who can install a closed-test build, where the settings live in Play Console, and what to ask a tester before you change anything.

Why a tester can join but still can't install

Being on your tester list and being allowed to install are separate checks. The tester list (an email list or a Google Group) controls who may opt in. Country targeting controls which Play countries can actually get the release.

Google's Can't find an app help page puts it plainly for users: "you'll only be able to see apps and content that are compatible with your Google Play country." A tester can be correctly invited and opted in, and still be outside the countries your closed track targets.

Play country is the account's country, not where the tester is

This is the detail most people miss. Google's country targeting article says: "Country targeting is based on the user's Play country (that is, where their account is registered), not their current location."

So:

• A tester whose Play account is registered in India still has an India Play country while travelling in Germany.
• A VPN doesn't change the Play country Google uses for targeting.
• Asking where a tester "is" can give you the wrong answer. Ask which country their Google Play account is set to.

A tester can check this in the Play Store app: tap the profile icon, then Settings, General, Account and device preferences, Country and profiles. These are the steps from Google's change your Google Play country article.

Where country settings live in Play Console

Google separates app availability from country targeting, and internal testing sits outside both:

Setting	What it controls	Where to find it
App availability	Countries for your production track, now and for future production releases	Production page, Countries/regions tab
Country targeting for a closed track	Countries that can get the release on that closed track	Testing > Closed testing, Manage track next to the track, Countries/regions tab
Internal testing	Not country-targeted at all	No country list; testers anywhere can get it

Google's article says: "By default, your testing releases match the country availability that you've set up for production." Its test setup guide, Set up an open, closed, or internal test, adds that "Changes to distributed countries and regions apply across all tracks," with internal testing as the exception.

In practice that means a country you never added to production, or removed from production, can also be missing from your closed test, even though you never touched the closed track.

How to give a closed track its own country list

If your testers are in countries you don't plan to launch in yet, you can stop the closed track copying production. According to Google's steps:

1. Open Play Console and select the app.
2. Go to Testing > Closed testing and click Manage track next to the track your testers joined.
3. Open the Countries/regions tab.
4. Click Unsync countries/regions so the track no longer follows production.
5. Click Edit countries, add or remove countries, and confirm.

Some limits apply. Google says you can customise testing-track countries only if your app has no app bundle uploaded to production, or it has one and at least one country is available in production. Turning sync back on is only possible when the track has no release rolled out, production targets at least one country or region, or pre-registration has started with at least one country other than "Rest of World".

If you run more than one closed track, check the track your testers actually joined. Each track has its own Manage track page.

Give the change time before retesting

Google's test setup article says that after a test is first published, "the test link can take several hours to become available to testers. Additional changes can also take several hours to become available."

So after you add a country, don't ask the tester to retry five minutes later and then assume the fix failed. Note the time you made the change, wait a few hours, and ask them to try again with the same opt-in link and the same Google account. Changing three settings at once makes it hard to tell which one fixed it.

Don't ask testers to change their Play country

Changing a Play country is a bigger step for the tester than adding a country is for you. Google's Play country article says:

• After setting a Play country, the user must wait at least 90 days before changing it, and at least 90 days between later changes.
• To set a new country, they must be in that location and have a payment method from that country.
• Members of a Google Family group can't change their Play country.
• Changing country can affect their Play balance, Play Points and access to some content.

Adding the tester's country to your closed track is almost always the right fix.

Internal testing ignores countries, but it isn't a shortcut

Google says country targeting doesn't apply to internal testing: "If an internal tester is located in a country where your app's production, open test, or closed test version isn't available, the user will still receive the internal test app."

That helps for quick team checks, but there are two catches:

• If your personal developer account was created after November 13, 2023, Google's testing requirements article requires a closed test with at least 12 testers opted in continuously for at least 14 days before you can apply for production access. An internal test doesn't meet that.
• Google's test setup article says: "A user who opts into your app's internal test is no longer eligible to receive an open or closed test." They must opt out of the internal test first.

So don't move a tester to internal testing to dodge a country problem if you need them in your closed test. Our internal vs closed testing guide covers when each track makes sense.

What about the 14-day count?

Google's requirement is written in terms of testers who are opted in: at least 12, continuously, for the 14 days before you apply. We couldn't find any Google statement about whether an opted-in tester who can't install, because of country targeting, still counts. Don't rely on it either way.

What we do know is that Google may ask for more testing if there was "insufficient tester engagement during the testing period," per the testing requirements article. A tester who can't install can't use the app or send feedback, so fix country access early, ideally before day one. For how to track each tester's continuous days, see how the 14-day testing window works.

If the country is fine, check the device

When the tester's Play country is on your list and you've waited a few hours, look at the other common blocker. Google's Can't find an app page also lists device compatibility: "You can only download or use an app on your device if the app is compatible with that device." Compare the tester's device and Android version with your app's requirements and any device exclusions. Our guide on inviting testers to a closed test walks through the other access checks, such as the wrong account or an unpublished release.

A message you can send a tester

Thanks for joining the test. To help me fix the install problem, could you tell me:

1. The Google account email you used to join.
2. Your Google Play country (Play Store, profile icon, Settings, General, Account and device preferences, Country and profiles).
3. Your phone model and Android version.
4. The exact message you see, or a screenshot. Please don't change your Play country. I'll update the test settings and let you know when to try again.

Checklist before your closed test starts

• Decide which countries your testers' Play accounts are registered in, not where they live.
• Check the Countries/regions tab on the exact closed track they'll join.
• If production doesn't include those countries, unsync the track and add them.
• Publish, then allow several hours before sending the opt-in link.
• Ask one tester per country to confirm they can see Install.
• Keep a short log of when you changed settings and which testers confirmed access.

Our free closed testing checklist includes this check alongside the rest of the setup.

If you use a tester service

Whoever supplies your testers, ask which countries their Play accounts are registered in before you narrow your closed track's country list. 12Testers14Day offers done-for-you Google Play closed testing: the Basic package is $15 for one app, with 14 testers for 16 days as a buffer above Google's 12 testers for 14 days (see pricing). Our site doesn't publish where tester accounts are registered, so if your app is limited to certain countries, contact the team before you buy. Google decides production access, and no service can promise approval.

FAQ

Does a VPN help a tester install a closed-test app from another country?
Google says country targeting uses the account's Play country, "not their current location," so a VPN doesn't change it.

My app has no production release. Can I still choose countries for a closed test?
Google says you can customise testing-track countries if no app bundle has been uploaded to production. Check the closed track's Countries/regions tab to see what's selected.

I added the country. Why can't the tester install yet?
Google says changes can take several hours to reach testers. Wait, then retry with the same account and link before changing anything else.

Can I just use internal testing for testers in other countries?
Internal testing ignores country targeting, but it doesn't meet the closed-testing requirement for new personal accounts, and a tester in your internal test can't receive your closed test until they opt out of it.