“Your device isn't compatible with this version”
Google Play filters the tester's phone out because of the app's manifest or a device exclusion. The developer finds the reason in the Play Console's Device catalog and fixes the manifest or the exclusion.
What you see
The tester became a tester, but the Play Store shows “Your device isn't compatible with this version” instead of an install button.
Why
Google Play decides from the build and the Play Console settings which phones get the app. The usual filters: a minimum Android version above the phone's, a hardware feature marked as required, native libraries that leave out the phone's CPU architecture, or a device excluded in the Play Console.
What to do
For the developer:
- Note the tester's phone model and Android version: Peerbeta lists the testers' phones.
- In the Play Console, open “Monitor and improve › Reach and devices › Device catalog”, search the model and read its status for the closed testing track.
- “Unsupported”: fix the manifest. Mark optional features with
android:required="false", add the missing ABIs, or lowerminSdk. - Excluded by a rule or by hand: remove that exclusion.
- Upload a new release with a higher version code.
For the tester: there is nothing to change on your phone. Before the install, you can free the seat at no cost.
What Peerbeta does
When failures gather on one phone model while others installed the app, the diagnosis tells the developer. Peerbeta only invites testers whose Android version meets the app's minimum.
Was this helpful?
Your feedback shapes what we write next.
The phone's Android version is too old for the app
Next →“Not available in your country”: the country isn't on the track