Please go back to the iOS desktop, and then open Settings-General-Profile and Device Management. Then, click the corresponding profile to enter, and then click the Trust button. For specific solutions, please refer to: Running Enterprise Application.
After the application installation, the icon turns into a dark icon, or a prompt "XXX cannot be installed" pops up.
If you are the developer of the application, please check whether the signature of the application is correct. This problem usually occurs because the signature of the application is incorrect. Generally speaking, for the Adhoc signature mode, it is very important to check whether the current device UDID has been registered; For internal signatures (that is, corporate signatures), it is important to check whether the certificate has been revoked. If you are not the developer of this application, please contact the developer to solve it.
After clicking the "Install" button in the webpage, the prompt "Do you want to install" does not pop up, or the installation failed.
The reason for this problem is generally because users have installed the same application from Apple's official App Store. The solution is to delete the previously installed application from your device and then install it from Dandelion.
When installing the application, the message "Cannot connect to www.pgyer.com" will appear.
This problem is generally caused by the cache error of the user's network or mobile phone. You can try the following two methods to solve it:
Restart the phone, and then try to reinstall it.
Change the network environment, such as changing a Wi-Fi hotspot, or changing from Wi-Fi to 3G/4G, and then re-installing.
Other reasons that may cause the application installation to fail:
Reason 1: When the developer packages the App and exports the installation package file (. Ipa file), he chose the App-Store mode.
When exporting. Ipa file of iOS, some developers choose App-Store mode. Yes. The ipa file exported in this way is only suitable for uploading to Apple App Store, and cannot be installed through dandelion. If. The ipa file is exported in this way, and the "App-Store version" will be displayed when dandelion is uploaded to dandelion, which cannot be installed through dandelion.
Reason 2: Export the installation package file (. Ipa file), peer-to-peer mode is selected, but the device UDID is not added.
When exporting the installation package file of iOS, if the Ad-hoc mode is selected (generally used for Apple's personal developer account), then if a device can be installed, the UDID of this device must be added to the certificate file (. Mobileprovision file) is used when exporting the installation package before installing it on this device.
After the installation package file exported by Ad-hoc mode is uploaded to Dandelion, Dandelion will be displayed as "beta version", and the list of UDID included in the certificate of the installation package will be displayed in application management. The developer can check whether the device's UDID has been added to the certificate of the installation package according to the displayed UDID list.
Reason 3: Export the installation package file (. Ipa file), internal mode is selected, but the certificate has expired or been revoked.
When exporting the installation package file of iOS, if In-house mode is selected (generally used for Apple enterprise developer account), if it cannot be installed at this time, the developer can check whether his enterprise developer certificate has expired or been revoked. Due to Apple's strict management of enterprise developer certificate, if the developer uses it improperly, the enterprise certificate may be revoked by Apple, and the installation package derived from the revoked 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 of the iOS application determines which devices the iOS application can be installed on. For example, if an application only adds the arm64 architecture to Xcode, the final packaged installation package file will not be installed on subsequent devices such as iPad mini and iPhone5 after being uploaded to Dandelion (because these devices are not arm64 architecture). In other words, if it needs to be installed on a device, the application must support the architecture of the device.
So the correct solution is to let the App support as many architectures as possible when generating the App installation package.
The specific operation method is: in XCode-Build Settings-Architecture, add armv7, armv7s and arm64, so that all devices can be installed. Then, set "Build Active Schemas Only" to the number of schema types supported by each iOS device. Please click here to view it.
Reason The iOS system version supported by App does not match the current device system version.
Too low or too high version of iOS system supported by App may lead to unsuccessful installation of App. For example, if an App is set with a system that only supports versions above iOS 1 1.0, it cannot be successfully installed on a system below this version.
So the solution is also very simple, try to make the App support a wider system version.
The specific operation method is: in XCode-General-Deployment Info-Deployment Target, set an App with the lowest version as possible, such as iOS 6.0.
Reason 6: This 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 application installation will also fail. The solution is simple. Users only need to delete the original application installed on the device, and then reinstall the new application.
Reason LSRequiresIPhoneOS in Info.plist file is not set, or it is not set.
For iOS applications, if LSRequiresIPhoneOS in the Info.plist file is not set, or no is set, then the installation package (. Ipa package) will not contain the payload folder, but will be replaced by a folder named Applications. Such an installation package will be judged invalid by iOS at the time of installation, so it cannot be installed correctly.
The solution is also very simple, just set LSRequiresIPhoneOS in the Info.plist file to YES, and then repackage it. The specific operation is as follows: Open the Info.plist file in Xcode, and then check whether lsRequirePhoneOS has been set. If not, add one, and then set the type of lsRequirePhoneOS to Boolean and the value to YES.
After setting it up, you can see that the value of the iPhone environment required by the application shown in the Info.plist file is YES.
In addition, you can also use Dandelion's Mac OS client to package and upload the App. Dandelion's Mac OS client will automatically deal with this problem when packaging the installation package.
Cause 8: Network interruption or abnormality.
In this case, users can check whether the network connected to their mobile phones is stable and the speed is normal. Can you open another website, or change to Wi-Fi, or change from Wi-Fi to 3G/4G, and then reinstall?
After trying in this way, the problem can usually be solved.
I tried the above scheme, but I still can't solve it.
If the problem cannot be solved after the above troubleshooting, you can use Dandelion's Mac OS client to view the installation log.
Dandelion's Mac OS client provides the function of viewing the App installation log in real time. Developers can conveniently and accurately judge the specific reasons for installation failure according to the installation log of the App. For details, please see: Check the installation log of iOS.
From the link: /p/73e77ff62f48
Reference document:? /p/ 128ceffcb399