Troubleshooting IOS App installation Failures

Objective

IOS Beta application in the installation, many people have encountered the installation failure, the reasons for installation failure is more, the following we will be some common causes summarized below, convenient for developers to troubleshoot.

"Unable to download application" during app installation

Reason one: When exporting the IOS APP's installation package files ( .ipa files), the App-store method is selected.

...

Reason two: When exporting the IOS APP's installation package file ( .ipa file), the Ad-hoc method was selected, but no device UDID was added.

...

Reason three: When you export an IOS App installation package file ( .ipa file), the in-house method is selected, but the certificate has expired.

When exporting an IOS installation package file, if you select the in-house method (typically used for an Apple Enterprise Developer account), the developer can check if the Enterprise Developer certificate has expired if it fails to install. Because Apple for Enterprise Developer Certificate Management is more stringent, so developers if used improperly, may lead to Enterprise certificate is blocked, the enterprise certificate is sealed after the export of the installation package, is not installed correctly.

Reason four: Developers did not set the correct Architecture in Xcode when they generated the app installation package.

The iOS app's Architecture (architecture) determines which device models The iOS app can install on. For example, if an app adds only arm64 this type of Architecture to Xcode, the final packaged package file will not be installed after it is uploaded to the dandelion for the following devices, such as the IPad Mini, IPhone5, and so on (because these devices are not arm64 Schema). In other words, if you need to be able to install on a device, the APP must support the Architecture of that device.

So, the right solution is to make the app support more Architecture as much as possible when building the app installation package.

How to do this: in Xcode - Build Settings - Architecture , add armv7 ,, armv7s arm64 , so that all devices can be installed. Then, "Build active architecture only" set to NO . The type of Architecture supported for each IOS device.

"Build active architecture only"Set toNO

Reason five: The IOS system version supported by the APP does not match the current device system version.

...

Reason six: The developer is uploading a cracked IPA installation package, or an IPA installation package generated using the cracked Xcode package, or an IPA installation package generated via ITunes.

...

Cause seven: The app is already installed on your device, and the apps you've installed and apps you want to install are packaged with different certificates.

...

Reason eight: Info.plist LSRequiresIPhoneOS there is no setting in the file, or set NO .

...

Cause nine: A network outage or an exception occurred.

...

Nothing happens when you install on IOS 8

This is due to a bug in iOS 8 where developers can try to open the "iOS 8 Install repair" feature in the app settings and then reinstall the app.

"Unable to connect to ssl.pgyer.com" appears when you install the IOS app

This problem is generally due to the user's network, or phone cache error caused by, you can try the following two ways to solve:

• Restart your phone, and then try reinstalling it.
• Change a network environment, such as a Wi-Fi hotspot, or switch from Wi-Fi to 3g/4g, and then reinstall.

When you try this way, you can usually solve the problem.

Troubleshoot the cause of the failure based on IOS installation logs

If the problem is still not resolved after troubleshooting the above, try using the Dandelion Mac OS client to view the installation log.

Dandelion's Mac OS client, provides real-time view of the app installation log, developers can easily according to the app's installation log, to accurately determine the specific installation failure reasons.

Above excerpt from: http://www.pgyer.com/doc/view/ios_install_failed

The problem I encountered was the compilation option

"Build active architecture only"Set to Yes


The cause of the problem is explained below:

This property is set to Yes, which compiles faster at debug time and compiles only the current version of architecture.

When set to No, all versions are compiled.

This is the device corresponding to the architecture:

armv6:iphone 2g/3g,ipod 1g/2garmv7:iphone 3gs/4/4s,ipod 3g/4g,ipad 1g/2g/3g

Armv7s:iphone5, IPOD5

The compiled version is backwards compatible, such as you set this value to Yes, compiled with iphone4 is the ARMV7 version, Iphone5 can also run, but the ARMV6 device cannot run.

Therefore, the general debug when you can choose to set the yes,release when you want to change to no, to adapt to different devices.

Troubleshooting IOS App installation Failures