Shulou(Shulou.com)06/01 Report--

This article shows you the reasons for the failure of iOS application installation, the content is concise and easy to understand, it will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

Troubleshooting of failed installation of iOS application

1. When launching an application in iOS 9, the prompt "untrusted enterprise developer" appears.

Open the settings-general-description file (called device management after iOS 9.2) in the system, and you can see a description file similar to the Chinese character of the prompt that just popped up. Then, click the corresponding description file to enter, and then click the button to trust

two。 After clicking the "install" button in iOS 9, there is no pop-up "install" prompt?

This problem is caused by a Bug of iOS 9. The premise of this problem is usually due to the fact that users have already installed the same app from Apple's official App Store. The solution is to remove previously installed applications from the device and then install them from the dandelion.

3. Why is it that in iOS 9, after clicking the "install" button, there is no response and there is no application icon on the desktop, but the network icon on the status bar is turning?

This is due to a Bug in iOS 9. Although there seems to be no response, the app has already been downloaded and installed in the background, as evidenced by the turning of the web icon on the status bar. At this time, just wait a little longer, and the application will be displayed on the desktop after the installation is completed.

4. When installing the iOS application, the prompt "cannot connect to download.getssl.cn" appears.

This problem is usually caused by the user's network or mobile phone cache error, you can try the following two ways to solve it: restart the phone, and then try to reinstall it. Change to a network environment, such as a Wi-Fi hotspot, or Wi-Fi to 3G/4G, etc., and then reinstall it.

5. Other reasons that may cause applications to fail to install:

Reason 1: when exporting the installation package file (.ipa file) of iOS App, the App-Store mode is selected.

When exporting iOS's .ipa files, some developers choose App-Store, which is only suitable for uploading to Apple's App Store and cannot be installed on their own websites.

Reason 2: when exporting the iOS App installation package file (.ipa file), the Ad-hoc mode is selected, but the device UDID is not added.

When exporting the iOS installation package file, if you choose the Ad-hoc method (generally used in Apple's personal developer account), then if you want a device to be installable, you must add the UDID of that device to the certificate file used when exporting the installation package. Mobileprovision file), can be installed on this device.

Reason 3: when exporting the iOS App installation package file (.ipa file), the In-house mode is selected, but the certificate has expired.

When exporting the installation package file of iOS, if you choose In-house (usually used in Apple Enterprise developer account), developers can check whether their enterprise developer certificate has expired if it cannot be installed. Because Apple is strict with the enterprise developer certificate management, if the developer uses it improperly, the enterprise certificate may be blocked, and the installation package exported by the sealed enterprise certificate cannot be installed correctly.

Reason 4: when generating the App installation package, the developer did not set the correct Architecture in Xcode.

The Architecture (architecture) of the iOS application determines which device models the iOS application can be installed on. For example, if an application adds only arm64 Architecture to Xcode, the final packaged installation package files uploaded to dandelion cannot be installed for the following devices such as iPad mini, iPhone5, etc. (because none of these devices are arm64 architectures). In other words, if you need to be able to install on a device, App must support Architecture for that device.

Therefore, the correct solution is to make App support as many Architecture as possible when generating the App installation package.

The specific operation method is: in the Xcode-Build Settings-Architecture, add armv7, armv7s, arm64, so that all devices can be installed. Then, set "Build active architecture only" to NO. The Architecture types supported for each iOS device. Please click here to see.

Reason 5: the iOS system version supported by App does not match the current device system version.

The low or high version of the iOS system supported by App may prevent App from being installed successfully. For example, if an App is set up to support a system greater than iOS 7.0, then the installation will not be successful if it is installed on an iOS 6.1system.

Therefore, the solution is also simple, and we should try to make App support a broader system version as much as possible.

The specific operation method is: in Xcode-General-Deployment Info-Deployment Target, set a version of App as low as possible, such as iOS 5.0.

Reason 6: the developer uploaded a cracked ipa installation package, or an ipa installation package generated by cracking Xcode, or an ipa installation package generated through iTunes.

Any installation package generated by any non-Xcode (or Xcode command-line tool) cannot be installed correctly on the device (except for jailbreak devices). Common incorrect ways to package ipa are: export installation package files through iTunes, export installation package files through iTools, and so on. This type of App is unsigned and cannot be installed.

The right way is to use a normal Apple developer certificate to generate an ipa installation package from an uncracked Xcode package.

Reason 7: this App is already installed on the device, and the installed App and the App to be installed are packaged with different certificates.

In this case, the App installation will also fail. The solution is simple. Developers only need to delete the App already installed on the device, and then reinstall the new App.

Reason 8: the LSRequiresIPhoneOS in the Info.plist file is not set, or NO is set.

For iOS's App, if LSRequiresIPhoneOS is not set or NO is set in the Info.plist file, the installation package (.ipa package) exported by Xcode will not contain the Payload folder, but will be replaced by a folder called Applications. When installing, such an installation package will be determined by iOS to be invalid, so it cannot be installed correctly.

The solution is also simple, just set the LSRequiresIPhoneOS in the Info.plist file to YES, and then repackage it. The specific action is: open the Info.plist file in Xcode, and then check whether LSRequiresIPhoneOS is set, if not, add one, and then set the type of LSRequiresIPhoneOS to Boolean and the value to YES.

Once set up, you can see that the value of Application requires iPhone environment shown in the Info.plist file is YES.

Reason 9: the network is interrupted or abnormal.

In this case, users can check whether the network connected to their mobile phones is stable, whether the speed is normal, and so on. You can try another website, or change a Wi-Fi, or change from Wi-Fi to 3G/4G, etc., and then reinstall.

The above is the cause of the failure of iOS application installation. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.