Summary of AIR for iOS development issues

Yesterday finally successfully submitted the application to the App Store, personally feel that using air as an iOS development is a hole ah. After the problem, ask Apple technical support, people say "for non-xcode environment problems caused by development and release, we can not find the corresponding solution in the database". Ask Adobe's technical support, "Do you follow the Developer Center tutorial?" "Yes" "can you successfully generate an IPA file?" "Yes" "OK, then your question should go to Apple's technical support" .... i + +, almost a kind of in the celestial petition was buck feeling.

So, I'm going to keep a record of my problems here so that I can remember and help the same students who have the same application for air development iOS.

1. We understand 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, download the build after uploading CSR to iOS Developer Center

1-3.P12 format certificate file, download the CER file from the iOS Developer Center and convert it in MAC format to export, this file determines whether you can generate an IPA file in fb (Flash Builder)

1-4. Configure profile *.mobileprovision, associate the Udid of the device, and create and download it in the iOS Developer Center. This file determines which devices the IPA file will run on in your development process.

In the end, the files required to generate an IPA in FB are 1-3 and 1-4, and I've been a little more likely to think that there's no direct relationship between the 2 files, but in fact once you've replaced the CSR file in the iOS Developer Center, your original configuration profile will all be invalidated. Needs to be recreated and downloaded. I did not re-create and download the mobileprovision file after I replaced the CSR file, this is the 1th error I made

2. In the tutorial provided by the Adobe Developer Center, the text "will generate a CSR for iOS developer/distribution Certificate", "Generate an iOS developer certificate or an iOS distribution certificate as needed". It means that thecer, P12, and mobileprovision files have 2 categories, one corresponding to the development phase, and one corresponding to the distribution (i.e. release) phase (distribute ). that is, I want to debug or run my program on my device, I need to select the P12 file exported by the developer certificate CER file and the Mobileprovision file for development that was created and downloaded in the iOS Developer Center when generating the IPA. , and when I export the release version of IPA to the App Store, you need to select the P12 file exported by the Distributor certificate and the Mobileprovision file for distribution. forgot to update the P12 and Mobileprovision files when exporting the release, this is the 2nd mistake I made

3. To undertake 2, when exporting the P12 certificate for distribution, you need to be aware of a detail that is not available when exporting the P12 certificate for development. Before you export the distribution P12 certificate, you need to first create a CER file in the Developer center and then click the link below to download a CER file that starts with a wadr name, and then add the file to the keychain under your Mac, which is accompanied by an Apple signature when you export the P12 file. If you do not have this step directly select Export P12, you will not be able to verify the certificate signature by submitting the app. The 3rd error I made was not downloading Wadr and adding a keychain before exporting the P12 certificate for distribution.

4. In 1, I mentioned "replacing the CSR file" and under what circumstances would we need to replace the CSR file? This involves a very vague and very delicate question. In my release process, encountered a scenario: on the device can be debugged and run, but after the application has been published after the application has been unable to pass the validation, and to ensure that the above mentioned 1, 2, 3 are no problem, so that people think not to ride elder sister. Finally found the problem: when generating a CSR file, in addition to filling out the developer account mailbox, you will also need to fill out a common name (common name), and this name must be the name you fill in the application for iOS developer account. And the pit-daddy is, this consistency requirement is only verified when the app is submitted, that is, before the development phase, even if the name is scrambled, it will not affect you to debug or run the program on the device. The last thing I found was the name comparison that I entered when I generated the CSR file and the name shown in the certificate has a space missing between first name and last name .... (There is another way of saying that the foreign programmer's authentication method is last name in the previous first name in the post) when the CSR file generated in the common name and the iOS developer account name is inconsistent, this is my 4th mistake