iOS apps

Reading the iOS device console logs

Capturing live installd and itunesstored error codes with macOS Console.app or idevicesyslog when an OTA install fails.

Why iOS shows generic "Unable to Install" alerts

For security reasons, iOS shows testers a single generic "Unable to Install" dialog regardless of whether the failure was caused by a missing UDID, mismatched bundle identifier, corrupted entitlement, or insufficient storage. Exact failure codes are written to the system unified log by installd and itunesstored.

Method 1: macOS Console.app (no extra tools required)

  1. Connect your iPhone or iPad to a Mac via USB and tap Trust This Computer on the device.
  2. Launch Console.app (Applications -> Utilities -> Console) and select your iPhone in the left sidebar.
  3. In the top-right search bar, type process:installd (press Return) or process:itunesstored, then click Start Streaming.
  4. Tap Install application on /i/{hash} in Safari on your iPhone and watch the log output.

Method 2: Command line via libimobiledevice

# Install libimobiledevice on macOS or Linux and filter live OTA install events:
idevicesyslog | grep -E "installd|itunesstored|MIInstallerErrorDomain"

Common MIInstallerErrorDomain codes

  • 0xe8008015 (ProvisioningProfileNotValid / Missing UDID): Device UDID is not in embedded.mobileprovision or entitlements do not match the profile.
  • 0xe8008016 (Entitlements mismatch): The .app binary requests an entitlement (such as Push or App Groups) not authorized by the provisioning profile.
  • 0xe800801c (No code signature): Binary inside Payload/*.app is unsigned or modified after signing.
  • ApplicationVerificationFailed (Bundle ID conflict): An App Store or differently signed app with the same CFBundleIdentifier is already installed—delete the existing app first.