When developing apps across platforms, developers will always encounter problems, such as packaging failures and so on, especially for iOS, because of its limitations can cause some situations (such as certificate upload problems, etc.), the small sum summarizes several Appcan online iOS packaging failure common situations and troubleshooting techniques, Troubled students can be used as a reference, to troubleshoot the problem.
Packaging failures can be divided into the following scenarios:
1, plug-in repeated check: Please check the "public plug-in" and "My Plugin" (self-uploaded plugin) whether there is a duplicate plugin.
2, certificate issues: Please refer to the Development Guide →ios certificate application process Guidelines document, the Apple website correctly apply for the certificate. After the certificate upload inspection does not mean that the certificate must be normal, just to verify that your profile is legitimate, the specific need to follow the tutorial re-application.
3. Code problem: Please check whether the project code is uploaded to the server, and there is no config file.
4, plug-in problems: check whether you use custom plug-ins, if there is, remove the custom plug-in packaging, if the package is successful, the package failed to isolate the custom plug-in caused.
Normal troubleshooting package failure techniques:
1, first use the default official certificate for packaging, such as the jailbreak certificate is packaged properly, if normal means that you upload a certificate there is a problem.
2, second, download the failure log, check the log in the relevant information, whether there are codesign, Provisioning profile, signing word, mostly certificate issues, re-upload the certificate, or change a browser to clear the cache and try again;
Search log for the existence of error words, can be based on the description of these error, to determine whether a plug-in caused by, or the existence of Chinese characters in the file;
If you do not have these words, most of the packaging is not finished, please re-pack to try.
3, upload certificate detection passed, still packaging failed? One is to verify the type of the certificate, the "Detection certificate" button is to help users detect the application of the certificate password is consistent with P12, and read the description of the app IDs; the second is the certificate profile that you requested. Mobileprovision may have problems, please re-apply according to the documentation tutorial.
Special Note:
The Enterprise Account ($299) has ad-hoc distribution and in-house distribution. Ad-hoc has 100 restrictions, in-house no device restrictions. The Enterprise Account (¥299) certificate needs to be uploaded to the platform's corresponding iOS Enterprise certificate.
Personal accounts and company accounts ($ $) include Ad-hoc distribution and App Store distribution, which also ad-hoc 100 restrictions, and App Store distribution can only be posted to the App Store, not Do other uses. The personal account and the company account ($) certificate are uploaded to the platform's corresponding iOS release certificate, as in the second tab.
4, online packaging prompt generation failure appids not match or compile FAILDM, generally the certificate and IDs do not match, bundle-identifier must be consistent with the appids of the certificate, follow the process to rebuild the certificate.
5. Carefully check whether the folder name or file name has Chinese characters in the project.
6, clear the browser cache and certificates, re-upload.
More development skills can be logged in Appcan official forum http://bbs.appcan.cn, for detailed understanding, technology Daniel Shared N Multiple development cheats, more technical experts full-time for your doubts.
10 minutes, Appcan help you solve cross-platform development app issues!