On this page
The problem
Testers reach your closed test page but see 'This app is not compatible with your device'.
Why it happens
Google Play filters installs by what your release actually supports: declared Android version requirements, CPU architecture and device features, screen sizes, and target API level. A mismatch with the tester's device triggers the incompatibility message.
The quick fix
Ask testers for their exact device model and Android version, then compare it against your release's declared requirements in Play Console.
Step by step
Find the device requirements
In Play Console, open your release and note the supported Android versions and any declared device features.
Match the tester's device
Confirm the tester's Android version is within range and the device supports the features your app declares (for example, camera, sensors, 64-bit only).
Publish a corrected release
If requirements are stricter than needed, adjust them in your release and submit it for review again.
Things to check
- Android version range in the release
- Declared device features and 64-bit requirement
- Tester's actual device model and OS version
If this didn't work
- Check whether the app is an APK-only build that excludes the tester's CPU architecture.
- Test with the exact same device model on a fresh Google Account.
Common mistakes
- Ship testing builds that need features unavailable on budget devices most testers own
- Ignoring architecture splits in the app bundle
When to contact Google
If the same released build works on some devices but not others with no apparent requirement mismatch, use Play Console support contact options with device logs.
Sources & references
Official Google documentationThese links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.
Last reviewed August 17, 2026 · Google Play requirements change — verify in the Play Console.