This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 52%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFS%3C/text%3E%3C/svg%3E)
The application can't be installed because it is incompatible with the device 0xC7D24FBC. we are getting this error after deploying private google play store application from Intune. What should we do to resolve this issue. Please help us. its very urgent request.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 4%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFS%3C/text%3E%3C/svg%3E)
We have asked our developer to do below changes after this changes its working fine.
the tablet we are trying to push the app doesn't support the
uses-permission call_phone.
remove that permission in the manifest or try add:
<uses-feature android:name="android.hardware.telephony" android:required="false" />
Directly under it.
<uses-feature android:name="android.hardware.telephony" android:required="false" />
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 35%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZM%3C/text%3E%3C/svg%3E)
@Farooqui Shahzaduddin Mohammad Hanif, Thanks for posting in Q&A.
For the error message, based on my experience, here are some possible causes I can think.
• The app is not able to be installed on your specific Android device.
• There are some limitation from Google side. Sometimes, the app developer has configured native platform info in their manafest incorrectly or not specifying device architecture. Sometimes, App developer will modify the App requirements to be matching exactly the Android device's hardware.
To clarify our issue, you can manually install the app on the affected to see if it can be installed successfully. If no, that means the app has issue to install. You can contact the app developer to look into the issue. If the app can be installed manually, then we suggest contact google support to look into the limitation.
Thanks for your understanding and have a nice day!
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
@ arooqui Shahzaduddin Mohammad Hanif, How is everything going?
I am writing to know if there is anything else we can do to help.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 31%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDW%3C/text%3E%3C/svg%3E)
I am experiencing the same issue with deploying our private app to android tablets. I have successfully installed the application on the tablet manually per your instructions. Could you provide the correct contact information for google support?
please ask developer to check whether all the permission given in Manifesto supports the device or not or you can check your own asking manifest from App developer.
the tablet we were trying to push the application doesn't support the uses-permission call_phone
2: either remove that permission in the manifest or try add:
<uses-feature android:name="android.hardware.telephony" android:required="false" />
Directly under it.
<uses-feature android:name="android.hardware.telephony" android:required="false" />