Changes and Known Issues in iOS 8

Manifest Requires Matching Bundle Identifier

In iOS 8 and later, the device now checks that the bundle identifier in the manifest matches the app being installed. Previously, the device did not verify the bundle identifier, and apps with different identifiers could be installed.

Loadly.io provides manifests with valid bundle identifiers.

HTTPS Mandatory for Manifest URL

In iOS 8 and later, the device will only accept the manifest from an HTTPS URL. Previously, the device could load the manifest from either HTTP or HTTPS URLs.

Loadly.io provides HTTPS for manifest URLs.

Automatic Provisioning Profile Installation

Starting from iOS 8.0, provisioning profiles are no longer manually installed. They are now embedded within the .app/.ipa file by Xcode and installed automatically when the app is installed. The provisioning profiles also no longer appear in the Settings app.

Background App Installation

In iOS 8.0 and later, app installation happens in the background. After tapping the install link, the app may appear to do nothing, but it is actually being installed on the Springboard. Check the Springboard to see the app icon.

Issues with iOS 7 to iOS 8 Updates

If an app was installed on a device running iOS 7 and the device was then updated to iOS 8, the development app may no longer be installable. This seems to be due to a cache related to the bundle identifier, which prevents the wireless installation. A temporary workaround used shortly after the iOS 8 release was to provide a different, fake bundle identifier in the manifest.