AIR for IOS development Summary

AIR for IOS development Summary

I finally successfully submitted an application to the app store yesterday. I personally feel that using AIR for IOS development is a pitfall. After a problem occurs, ask Apple's technical support. "We cannot find the corresponding solution in the database for problems caused by development and release in non-XCODE environments ". Ask adobe's technical support. "Have you followed the Developer Center tutorial ?" "Yes" "Can you generate the IPA file successfully ?" "Yes" "OK, so you should go to Apple's technical support for your problem "....

Therefore, I will record all the problems I encountered here so that I can forget and help my colleagues who are also applicable to IOS development using AIR.

1. We know that there are several types of files in IOS development:

1-1. Certificate Signing Request CSR file, generated under MAC

1-2.IOS developer/Distribution Certificate *. cer file, which is downloaded and generated by uploading CSR to the IOS Developer Center

Certificate files in 1-3.P12 format: download the cer file from the IOS Developer Center and export the file in the conversion format under MAC. This file determines whether you can generate an IPA file in FBflash builder.

1-4. The configuration profile *. mobileprovision is associated with the device's UDID, which is created and downloaded from the IOS Developer Center. This file determines the devices on which the IPA files generated during your development can run.

In the end, the files required to generate IPA in FB are 1-3 and 1-4. I previously thought that there was no direct relationship between these two files, however, once you replace the CSR file in the IOS Developer Center, all your original configuration profiles become invalid and need to be re-created and downloaded. I did not recreate and download the mobileprovision file after I replaced the CSR file. This is my 1st error.

2. in the tutorial provided by the adobe Developer Center, the original article "CSR will be generated to obtain the IOS developer/Distribution Certificate" "generate the IOS developer certificate or the IOS Distribution Certificate as needed" is as follows ". It means that there are two types of cer, p12, and mobileprovision files. One corresponds to the development phase, and the other corresponds to the distribution (publish) phase distrivision ). That is, I want to debug or run my program on the device, when generating IPA, You must select the P12 file exported from the developer certificate cer file and the mobileprovision file created and downloaded in the IOS Developer Center for Development; when I export the release version IPA and submit it to the app store, I need to select the P12 file exported from the issuer certificate and the mobileprovision file for distribution. I forgot to update the P12 and mobileprovision files when exporting the release. This is my 2nd error.

3. Undertake 2. Pay attention to the details when exporting the P12 certificate for distribution. This detailed step is not found when exporting the P12 certificate for development. Before exporting and distributing the P12 certificate, you need to first download a cer file starting with the WADR name in the page of creating the distribution cer file in the Developer Center, then add the file to the key string on the MAC, which will include the apple signature when you export the P12 file. If you do not have this step to export P12 directly, you will not be able to pass the certificate signature verification when submitting the APP. I did not download WADR and add the key string before exporting the P12 certificate for distribution. This is my 3rd error.

4. In section 1, I mentioned "replacing the CSR File". Under what circumstances should we replace the CSR file? This involves a very subtle question. During my release process, I encountered the following scenario: I can debug and run the configuration on the slave node, but I still cannot pass application verification when I submit the application after the release, and make sure that the first, second, and third mentioned above are all correct, so that you can't ride your sister. Finally, the problem is found: when generating a CSR file, in addition to entering the developer account mailbox, you also need to fill in a common name ), the name must be the same as the name you entered when applying for an IOS developer account. However, this consistency requires verification only when the APP is submitted, that is, during the development phase, even if the name is out of the box, it does not affect debugging or running programs on the device. The Last problem I found was that the Name comparison I entered when generating the CSR file and the Name displayed in the certificate was missing a space between First Name and Last Name .... There is also a saying on the Internet that the verification method for foreign programmers is that the Last Name is placed after the First Name.) The common names entered when the CSR file is generated are different from those in the IOS developer account, this is my 4th mistake.

Link: http://www.cnblogs.com/lovewx/archive/2014/07/17/3845151.html