"This app is not available for your device" usually means Google Play has filtered the tester's phone out because of what your app declares it needs: a minimum Android version, a required hardware feature, a form factor or a CPU architecture. Less often the same wording shows up because the tester's country isn't on your closed track, or because they're signed in with the wrong account. Start with your app's requirements, since that's what the message points at.
1. Your app's requirements exclude the device
If the country and account are right, look at your app itself. Google Play filters apps by what the build declares it needs. Common reasons a real device is excluded:
- Minimum SDK too high. If your
minSdkis above the Android version on the tester's phone, Play won't offer the app. - Required hardware features. A
<uses-feature>entry in the manifest marked as required (for example a specific camera or sensor feature) excludes devices that don't report it. Mark features as not required if your app can work without them. - Screen or form factor. An app declared only for certain screen types or form factors won't show on others.
- Native code. If your bundle only includes native libraries for some CPU architectures, devices with other architectures can't install it.
These are your app's settings, not Google's testing rules, so check your manifest and build configuration. Play Console also shows which devices your release supports, which helps confirm whether a tester's model is excluded.
Older or budget phones are often the ones that hit this, which is a good reason to test on a mix of real devices before you launch to everyone.
How to confirm a device is excluded
- Ask the tester for the phone model and Android version (Settings > About phone).
- Compare the Android version with your app's
minSdk. Android 10 is API level 29, Android 12 is API 31, and so on. - Open your manifest and list every
<uses-feature>entry that is required. Ask whether the tester's phone has each of them. - Look up the model in Play Console's device catalog, which shows whether your current release supports it and, if not, why.
- If you change a requirement, upload a new build to the closed track and send it for review; the tester can install once it's approved.
If the device is excluded on purpose, for example because your app genuinely needs a feature that phone lacks, that's a valid product decision. Just make sure the rest of your testers can install it.
2. If the device is compatible: country, account and opt-in
When the phone clearly meets your requirements, the cause is usually on the track or the tester's side. These have their own articles, so here is the short version:
- Country. Testing tracks have their own country list; Google says it "is synced with production by default", and you can change it under Testing > Closed testing > Manage track > Countries/regions. Testers in a country that isn't selected most likely can't get the closed test. Our testers are in Indonesia, so Indonesia must be on the list for GoPlayTester orders — see countries and regions for a closed testing track.
- Account. Testers must use the Google account you added to your list. If the Play Store is signed in to another account, see testers signed in with the wrong Google account.
- Opt-in and release status. A tester who hasn't accepted the opt-in link, or a release that isn't approved and published yet, can also produce confusing store messages. Work through testers can't find your app on Google Play, and check that you pressed Send in Publishing overview (why your tester invite isn't approved).
- Paid apps. Closed testers must purchase paid apps. That's a different message, but it surprises testers too.
A quick troubleshooting order
| Check | Where | Typical fix |
|---|---|---|
| Country on the track | Manage track > Countries/regions | Add the tester's country, send for review |
| Correct account | Tester's Play Store profile | Switch account, reopen opt-in link |
| Device compatibility | Manifest, minSdk, native libraries |
Lower requirements or accept the exclusion |
| Release status | Publishing overview | Send for review, wait, publish if managed |
If a single tester has a phone your app genuinely can't support, that's fine. Make sure you still have at least 12 testers who can install and use the app, since 12 opted-in testers for 14 continuous days is the requirement.
GoPlayTester's testers use their own real Android devices in Indonesia. If you want us to run your 14-day test, add Indonesia to your closed track as the guide explains and place an order.
