Google's rule doesn't say where your closed testers have to live. Testers in another country count the same as testers next door, as long as they're real people who opt in and stay opted in for 14 continuous days. The practical difference is setup: the tester's country has to be on your closed track's country list, and you should check that your app actually works for people there.
Does Google care where testers are?
The requirement is "a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days" (App testing requirements). There's no country condition in it. Each tester needs a Google account and must opt in through your link.
What Google does say is that it's good to recruit testers who "represent your app's intended future audience." That's advice, not a rule, and it's worth thinking about honestly. If your app is built for one specific local market, testers elsewhere may use it differently from your eventual users. If your app is for a general audience, location matters much less. Either way, describe your testers truthfully in the production access form.
The setting that matters: countries on the closed track
Closed testing tracks have their own country and region list. Google says that for testing tracks, "Country availability is synced with production by default", and you can Unsync countries/regions and Edit countries under Testing > Closed testing > Manage track > Countries/regions (Country distribution).
It follows that a tester in a country that isn't selected for the track likely can't get your closed test. Google doesn't spell out that consequence in one sentence, so treat it as likely rather than certain, but don't leave it to chance. If your testers are in Indonesia, Indonesia has to be on the list. The full walkthrough is in countries and regions for a closed testing track.
Two points that often reassure developers:
- Testing countries aren't launch countries. Once you unsync, the closed track's list is separate from production. Adding Indonesia for testing doesn't mean you have to launch there.
- Don't remove the country during the test. Unselecting a country your testers are in can cut them off and put their 14 days at risk. Our article on the 14-day counter and updates explains which changes are safe.
Check that your app works in the testers' country
Some apps behave differently by region, and a closed test is a good time to find out. Before testers start, consider:
- Region-restricted services. Payment providers, maps, streaming content or third-party APIs may limit some countries. If a key feature is blocked for testers, they can't really test it.
- Phone numbers and sign-up. SMS verification, address forms or phone number formats sometimes reject numbers from other countries.
- Language. If your app is only in one language, make sure testers can use it, or give them short instructions.
- Time and dates. Testers in a different time zone will exercise your date, time and notification logic in ways you might not.
None of these make testers abroad better or worse. They're simply real conditions your production users in other countries could also hit.
Time zones and the 14 days
The 14 days are measured as continuous opt-in, counted back from when you apply. A time zone difference doesn't change the rule, but it does affect coordination. For example, Indonesia's Western Indonesia Time (WIB) is UTC+7. If you and your testers are many hours apart, plan for:
- replies to bug reports arriving overnight for you
- updates you ship in your evening reaching testers in their morning
- a few hours of margin when you calculate day 14, so you don't apply too early
When testers can't install
If testers abroad opt in but can't install, the cause is usually one of three things: their country isn't on the closed track, they're using a different Google account in the Play Store app, or their device doesn't meet your app's requirements. Work through this app is not available for your device and opt-in link not working.
Device variety is a benefit here, not a problem. Testers in another market may use phones you haven't tried. Real testers on real devices explains why that matters.
A note on Android developer verification
Indonesia is one of the first countries where Android developer verification is enforced. From September 30, 2026, Google says apps "must be registered by verified developers in order to be installed and updated on certified Android devices in Brazil, Indonesia, Singapore, and Thailand." This is a separate program from the 12-tester rule. For Play apps, Google states that if you've completed Play Console's developer verification, "your identity is already verified and we'll automatically register eligible Play apps for you." If your Play Console verification is complete, there's likely nothing extra to do for testers in Indonesia, but check your Play Console for any notices.
How it works with GoPlayTester
Our testers are based in Indonesia. To run a test with us, you add our Google Group ([email protected]) to your closed track's testers and include Indonesia in the track's countries, then send the changes for review. Our setup guide walks through each step. Testing starts from 8 PM WIB in queue order once your testing link works.
Checklist
- The testers' country is selected on the closed track
- The country stays selected until production access is decided
- Key features work in that country (payments, sign-up, APIs)
- Testers can use the app's language, or have instructions
- You've allowed for the time zone when planning updates and day 14
- Your production access answers describe your testers honestly
If you need testers and are happy for them to be in Indonesia, you can order a 14-day test. Google makes the final decision on production access.
