foreword
When installing the iOS internal test application, many people have encountered the installation failure. There are many reasons for the installation failure. The following is a summary of some common reasons for the convenience of developers to investigate.
"Untrusted Enterprise Developer" when launching an app in iOS 9
This problem is because in iOS 9 and later versions, Apple has made stricter restrictions on enterprise-signed applications. For specific solutions, please refer to: The problem that the enterprise certificate cannot be used after being packaged, downloaded and installed
After clicking the "Install" button in iOS 9, there is no prompt to "install"
This problem is caused by a bug in iOS 9. The premise of this problem is generally because the user has already installed the same application from Apple's official App Store.
【Solution】
First delete the previously installed app from the device, and then 托管平台install it again.
Why in iOS 9, after clicking the "Install" button, nothing happens, 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 it doesn't seem to respond, the app has already started downloading and installing in the background, as evidenced by the rotating network icon on the status bar. At this time, just wait for a while, and the application will be displayed on the desktop after the installation is complete.
"Unable to download the app" during app installation
Reason 1: When exporting the installation package file (.ipa file) of the iOS App, the App-Store method is selected.
When exporting iOS .ipafiles, some developers have chosen a App-Storeway. The .ipafiles exported in this way are only suitable for uploading to Apple App Store, and cannot 托管平台be installed through. .ipaIf the file is exported in this way , 托管平台it cannot be installed on the upload.
Reason 2: When exporting the installation package file (.ipa file) of the iOS App, the Ad-hoc method is selected, but the device UDID is not added.
When exporting the installation package file of iOS, if the Ad-hocmethod is selected ( generally used for Apple personal developer account ), then, if you want a device to be installed, you must UDID add this device to the file used when exporting the installation package. The certificate file ( .mobileprovisionfile) can only be installed on this device.
After the installation package file exported by using Ad-hoc the method is uploaded 托管平台, 托管平台it will be displayed as , and at the same time, the list 内测版contained in the certificate of the installation package will be displayed in the application management . UDIDDevelopers can UDIDcheck whether a certain device UDID has been added to the certificate of the installation package according to the displayed list.
Reason 3: When exporting the installation package file (.ipa file) of the iOS App, the In-house method is selected, but the certificate has expired or been revoked.
When exporting the iOS installation package file, if the In-housemethod is selected ( usually used for Apple enterprise developer accounts ), at this time, if the installation cannot be performed, the developer can check whether his enterprise developer certificate has expired or been used. revoke. Because Apple has strict management of enterprise developer certificates, if developers use it improperly, the enterprise certificate may be blocked, and the installation package exported from the blocked enterprise certificate cannot be installed correctly.
Reason 4: The developer did not set the correct Architecture in Xcode when generating the App installation package.
The Architecture(architecture) of an iOS app determines which device models the iOS app can be installed on. For example, if an application only adds arm64Architecture in Xcode, after the final packaged installation package file is uploaded 托管平台, it cannot be installed for the following devices such as iPad mini and iPhone5 (because these devices are not arm64) architecture). In other words, if it needs to be installed on a device, the app must support that device Architecture.
Therefore, the correct solution is to make the App support as many as possible when generating the App installation package Architecture.
The specific operation method is: in Xcode - Build Settings - Architecture , add armv7, armv7s, arm64 , so that all devices can be installed. Then, "Build active architecture only" set to NO . Architecture Types supported for each iOS device . Please click here to view .
Reason 5: The iOS system version supported by the App does not match the current device system version.
If the iOS system version supported by the App during packaging is too low or too high, the App may not be installed successfully. For example, if an App is set to only support iOS 7.0 and above, then if it is installed on iOS 6.1, it will definitely fail to install successfully.
Therefore, we should try to make the app support as wide a range of system versions as possible.
The specific operation method is: in Xcode - General - Deployment Info - Deployment Target, set a version as low as possible for the App, such as iOS 5.0.
Reason 6: The developer uploads a cracked ipa installation package, or an ipa installation package that is packaged and generated by cracking Xcode, or an ipa installation package generated by iTunes.
Installation packages generated by any non-Xcode (or Xcode's command-line tools) cannot be properly installed on the device ( except for jailbroken devices ).
Common and incorrect ways of packaging ipa are: 通过 iTunes 导出安装包文件, 通过 iTools 导出安装包文件and so on. After uploading this type of App , the label prompt 托管平台will be displayed .未签名
【The right way】
Use a normal Apple developer certificate to generate the ipa installation package through the uncracked Xcode package.
Reason 7: The app has been 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 very simple, the developer only needs to delete the app that was originally installed on the device, and then reinstall the new app.
Reason 8: LSRequiresIPhoneOS in the Info.plist file is not set, or NO is set.
For iOS App, if there is no setting Info.plistin the file , or NO is set , then the installation package (package) exported by Xcode will not contain a folder, but will be replaced by a folder called. When such an installation package is installed, it will be judged as an invalid installation package by iOS, so it cannot be installed correctly.LSRequiresIPhoneOS.ipaPayloadApplications
【Solution】
Just set to YESInfo.plist in the file and repackage. The specific operation is: open the file in Xcode , then check if it is set, if not, add one, then set the type to Boolean and the value to YES .LSRequiresIPhoneOSInfo.plistLSRequiresIPhoneOSLSRequiresIPhoneOS
After setting, you can see that the value Info.plistdisplayed in the file is YES .Application requires iPhone environment
Reason 9: The network is interrupted or abnormal.
In this case, the user can check whether the network connected to his mobile phone is stable and whether the speed is normal. You can try other websites, or replace a Wi-Fi, or change from Wi-Fi to 3G/4G, etc., and then reinstall.