Can't Install an App on an iOS Device? Causes and Fixes
By Afrah Saleem · · 7 min read

Having trouble installing an app on an iPhone or iPad from a link? Often iOS gives no error message at all, or a short one that does not say what is wrong, which makes it hard to know where to start.
There is usually not one reason but a few possible ones. This guide goes through what testers see, what each behavior means, and what the developer should check.
First: which builds can be installed from a link
iOS only installs a build from a link when it is signed Ad Hoc, Development or Enterprise. App Store and TestFlight builds cannot be installed from a link, whichever service hosts the file. Ad Hoc and Development builds install only on devices whose UDID is in the build's provisioning profile; Enterprise builds do not need UDIDs. The signing in the .ipa you upload is the signing testers get, unless you re-sign it on AppForShare Pro or Team with a new ad hoc, development or enterprise profile, which saves a new build.
Behaviors testers see
The install prompt did not appear
Open the link in Safari. Links opened inside a chat or email app's own browser often do nothing when you tap Install. Copy the link and paste it into Safari.
Also check whether the same app is already on the phone from the App Store. A copy with the same bundle identifier that came from the App Store can stop the test build from installing over it. Delete the App Store copy first, then install the test build from the link again.
Nothing seems to happen
The prompt appeared, you tapped Install, and Safari shows nothing new. That is normal: iOS installs in the background. Go to the Home Screen, where the app icon appears with a progress indicator.
If the icon stays grey or dimmed, the download stalled or iOS refused the build. iPhone app icon stays grey after installing a test build explains how to tell the two apart and how to fix each.
"Unable to install" or "integrity could not be verified"
iOS downloaded the build and refused it. The usual causes are that this device's UDID is not in the build's provisioning profile, the profile or certificate has ended, or the build is signed for the App Store. Installing the same build again will not help; the developer has to fix the build. See iPhone "integrity could not be verified": fixing link installs for the checks in order.
The app installed but will not open: Developer Mode
On iOS 16 and later, Ad Hoc and Development builds open only after Developer Mode is turned on: Settings, Privacy and Security, Developer Mode, then restart the phone and confirm. The option appears once a build of that kind is on the phone. See how to turn on Developer Mode.
Untrusted Enterprise Developer
An Enterprise (in house) build will not open until the user trusts the developer on that device. Otherwise iOS shows an "Untrusted Enterprise Developer" message. On current iOS versions go to Settings, General, VPN and Device Management, tap the developer's profile under Enterprise App, then tap Trust. On older versions the same option is under Settings, General, Profiles or Device Management.
Unable to download
If the download does not start, check the internet connection first. Then make sure the phone is not behind a firewall or network filter that blocks .ipa downloads, as some company and school networks do, and that the phone has enough free storage for the app.
What the AppForShare install page tells you
iOS rarely says what is wrong, so AppForShare install pages check what they can before you tap Install. When the build cannot work on the phone that opened the page, a note above the Install button says so: the build needs a newer iOS version, it is an iPad only build opened on an iPhone, its profile has ended, it is signed for the App Store, or it is not signed. An install help list covers Safari, the Home Screen icon, Developer Mode, enterprise trust and "integrity could not be verified". See Install help.
The page cannot see your phone's settings, so Developer Mode and enterprise trust are steps to check, not a diagnosis. To know whether your device is in an Ad Hoc build, find your UDID at appforshare.io/udid and tap Remember this device; iOS install pages on appforshare.io then say whether your iPhone is in the build. See iPhone device check.
The most common causes in short:
- The provisioning profile has expired.
- The device's UDID is not in the provisioning profile.
- The device does not meet the build's requirements: minimum iOS version, device family (iPhone or iPad) or required capabilities.
- Not enough free storage.
Things to check as a developer
- The provisioning profile the build was exported with contains the tester's UDID. Registering the device in the Apple Developer portal is not enough; the profile has to be regenerated and the app built again.
- The UDID is real. Values that start with "ffffff" are not device UDIDs (see below).
- The build is an archive exported for Ad Hoc, Development or Enterprise, not a simulator build and not an App Store export.
- The profile and the distribution certificate are still valid.
- The tester's network does not block .ipa downloads.
More information
UDIDs in the provisioning profile
With a Development or Ad Hoc provisioning profile, the device's UDID has to be in that profile when you sign the app. In house builds for an Apple Developer Enterprise account do not need registered UDIDs.
Xcode embeds the profile in the app as embedded.mobileprovision. To see which devices a build includes, open the .ipa in the free IPA inspector, which runs in the browser and lists every provisioned UDID without uploading the file. On a Mac you can also unzip the .ipa, right-click the .app in the Payload folder, choose Show Package Contents, and read the profile with:
security cms -D -i embedded.mobileprovision
The UDIDs are listed under the ProvisionedDevices key:
<key>ProvisionedDevices</key>
<array>
<string>00008030-001A2B3C4D5E6F7A</string>
...
</array>
If a tester's UDID is missing, find the UDID on the iPhone with AppForShare, add it in the Apple Developer portal, regenerate the profile and build again.
Valid UDIDs
The UDID format depends on the device. Older devices use a 40 character hexadecimal string. Devices from 2018 onwards, starting with the iPhone XS and XR, use 25 characters with a hyphen after the first 8, such as 00008030-001A2B3C4D5E6F7A. You can read a valid UDID by connecting the device to a Mac (Finder) or a Windows PC (Apple Devices or iTunes), or directly on the device at appforshare.io/udid.
Apps cannot read the UDID. Apple removed that API years ago, and since iOS 7 apps that still call it get a fake value that starts with ffffff. Such a value does not identify a device and cannot be used in a provisioning profile.
Built architectures
Current iPhones and iPads run 64-bit (arm64) apps only. An archive built with the Release configuration and exported for Ad Hoc, Development or Enterprise includes the right architecture. A build made for the iOS Simulator cannot be installed on a device, and a Debug build with only the active architecture may not run on other devices, so share archived exports rather than Xcode's run builds.
Frequently asked questions
Why can I not install an App Store or TestFlight build from a link?
iOS only installs builds signed Ad Hoc, Development or Enterprise from a link. App Store and TestFlight builds install only through the App Store or the TestFlight app.
The icon appeared on the Home Screen but stays grey. What now?
Either the download stalled or iOS refused the build. Delete the grey icon, open the link in Safari on a stable connection and try again. If iOS then says Unable to install, the device is usually not in the build's profile or the profile has ended, and the developer has to build again.
How do I know if my iPhone is in the build?
Find your UDID at appforshare.io/udid and tap Remember this device. iOS install pages on appforshare.io then say whether your iPhone is in the build before you tap Install. Developers can also check the UDID list of an .ipa in the free IPA inspector.
Does AppForShare fix or re-sign builds that will not install?
AppForShare does not change the file you upload, and the install page explains why a build cannot install. When the cause is the profile, for example a missing device, Pro and Team can re-sign the iOS build with a new ad hoc, development or enterprise profile, with no rebuild, saved as a new build. Other causes need a fix and a new upload from the developer.
Where do I trust an enterprise developer on iOS?
Open Settings, General, VPN and Device Management, tap the developer's profile under Enterprise App and tap Trust.


