|Feature||Deploy on device|
When deploying or installing an iOS app on a device, the installation fails with an error message.
When deploying using a USB cable, the following error is displayed in the Output window in AppBuilder:
When installing the app on a device (for example, installing from a QR code), iOS displays an error message:
Unable to Download App. [AppName] could not be installed at this time
This is a generic error, which may be caused by a number of reasons. Some simpler ones include:
- Insufficient device storage.
- The minimum OS version specified in the app project properties is greater than the OS version of the device that tries to install the app.
However, in Telerik Platform development scenarios, the most common cause of this problem is incorrect provisioning of the app. Below you can find the most common provisioning problems that could lead to deployment failures:
- The device, that you are trying to install the app on, is not included in the app provisioning profile.
- You have enabled some Apple service on your device, for example, iCloud service, but you have not enabled the service for the App ID of your provisioning profile.
To address this problem, you should rule out the possible causes one by one. You can follow the steps below to do this:
- Check the device and confirm that it is connected to the internet and has enough free space to install the app on.
- Check the Deployment Target Version specified in Properties → iOS in AppBuilder. It should not exceed the iOS version of the device that you are deploying your app on.
- If you are using a Development or Ad Hoc provisioning profile, you need to make sure that the device UDID is included in the provisioning profile.
- Check the app for usage of any Apple services (Push Notifications, iCloud, HealthKit, etc.) and then confirm that these services are enabled in the App ID that you used in the iOS Dev Center to create your provisioning profile.
If the issue is not resolved on your side by following the steps above, you can try deploying a new blank app using the same provisioning profile, on the same device. This will show if the issue is with the provisioning profile or with your app and will help you focus your attention on the correct source of the issue. If the issue is with the provisioning profile, you can try creating a new certificate and profile for your app, keeping in mind the points listed above.