Can My 12 Testers Be in Different Countries? The One Catch

Yes. Google sets no country requirement for your 12 testers, and they can be spread across as many countries as you like.

What actually blocks people is a separate setting.

A closed testing track is limited to the countries you picked for it. A tester whose Play country sits outside that list cannot install the app, no matter how correctly they opted in.

This catches experienced developers because internal testing behaves differently, so the same tester who installed your internal build hits a wall on the closed one.

Globe with five tester pins, four inside the track country list shown in green and one outside it shown in red and unable to install — The testers are valid. The track’s country list is what decides who can install.

Does Google require testers in specific countries?

No. The requirement is 12 testers opted in continuously for 14 days [1]. That is the whole rule. It says nothing about where those people live, what nationality they hold, or how many countries they are spread across.

You can pass with 12 testers in one city, or 12 testers on four continents. Google counts opted-in testers, not passports.

Then why can my tester abroad not install the app?

Because country availability is set per track. It is a different control from the tester list.

When you pick countries for a closed testing release, testers can only reach the app if their Play country is in that selection [2].

So the sequence people hit is this. You add the tester’s email. They accept. They open the opt-in link.

Everything looks correct on your side, and they still see that the app is not available. Nothing is broken. Their country is simply not on the track.

Check the countries on the closed testing release itself, not on your production listing. They are set separately, and a release limited to one country during early testing is easy to forget about later.

Why did it work on internal testing but not closed testing?

This is the part that wastes the most time, and it is documented. Country targeting does not apply to the internal testing track at all. Google’s wording is explicit:

Country targeting won’t apply to apps on the Internal testing track. You can add users from any location to an internal test. 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 [2].

An internal test therefore proves nothing about whether your closed testers can install. If you validated your invite flow on internal testing with a friend overseas, that success does not carry across.

Track	Country targeting applies	Tester whose Play country is not selected
Internal testing	No	Installs anyway
Closed testing	Yes	Cannot install
Open testing	Yes	Cannot install
Production	Yes	Cannot install

What exactly is a Play country?

It is the country on the Google account, not the country the person is standing in. Google sets it from your location and your payment method, and it does not follow you when you travel [4].

That distinction matters when you recruit. A tester who moved from India to Germany last year may still carry an Indian Play country. What counts is the account setting, so ask them what their Play Store shows rather than where they live.

They also cannot flip it on demand to help you. Changing a Play country means being physically in the new country, with a payment method from it. Google also enforces a wait of at least 90 days between changes [4].

Can they just use a VPN instead?

No. This is where a small availability problem turns into an account problem.

A VPN changes the network route, not the Play country on the account. So it does not even fix the install failure it is usually reached for.

Making accounts to work around the geography is the version that does real damage. Google banned 80,000 developer accounts in 2025 [5].

Adding countries to your track takes seconds and carries no risk. There is nothing to gain from the workaround.

Should I deliberately spread testers across countries?

It is not required, and it is worth doing anyway.

Across the closed tests we have run, the varied records read best.

Twelve testers on one device model in one country produce a narrow record. A narrow record is also what artificial testing looks like from Google’s side.

Spreading testers across regions, devices and Android versions gives reviewers more to work with.

Treat it as a quality signal, not a rule. Never turn down a willing tester because of where they live. Daily use matters far more than geography.

Frequently asked questions

Do my testers have to be in the same country as my developer account?

No. Your account country and your testers’ countries are unrelated. A developer registered in India can run a closed test entirely with testers in Brazil, provided those countries are selected on the track.

How many countries should I select for a closed test?

Select every country your testers are in, at minimum. Many developers select all countries during closed testing and narrow the list at production, which removes this failure mode completely.

My tester is travelling. Will that break their opt-in?

No. Travel does not change their Play country, so their access does not change either. The 14 day clock keeps running while they are away, as long as they stay opted in and keep using the app.

Does adding a country later fix a tester who already failed?

Yes. Add the country, then have them retry the opt-in link. Changes to track settings take a few hours to propagate, so wait before concluding it did not work.

Do testers in different countries count differently towards the 12?

No. Every opted-in tester counts once, wherever they are. There is no weighting by region.

Can I test country-specific pricing this way?

Only for the countries on the track. If a tester’s country is not selected, they see nothing to price, so add the country first.

If you would rather not manage the geography

Option 1: verified testers assigned to you

Starter, ₹999 gives you 15 verified Android testers for the full 14 days.
Pro, ₹1,699 gives you 25 testers, plus a detailed ASO report and priority support.

Testers assigned within 6 hours, so your 14 days start today rather than after a week of asking.
They stay active for the full period.
Anyone who goes inactive is replaced.
A feedback report at the end, plus pre-filled answers for the 10 production access questions.
100% production access or your money back.

More than 10,000 apps have reached production this way. Submit your app to start.

Option 2: join a free Pack of 16

If you would rather trade time than money, the Testers Community app puts you in a pack of 16 developers. Everyone tests each other’s apps for 16 days, and inactive members get replaced.

Either way, check the full requirements before you begin. Walk through inviting testers properly so nobody falls at the opt-in step. And read why production access gets refused, so the record you build is one Google can approve.