iOS certificate request and release process

• What is a certificate?

This is the one that we downloaded to the local. cer file, which is often said to be the style of the development certificate and the publishing certificate, after we have applied for the certificate. The certificate in this. cer file format is for developers to use the device (that is, your Mac) to have a real-computer debug, to publish the app's permissions.

This is the one that we downloaded to the local. mobileprovision file, which is the style of the configuration file, after we have configured the certificate. The configuration file in this. mobileprovision file format is for developers to have a project (APP) that can have real-machine debugging, publishing permissions.

• Application process.

1. Request a Keychain file

Enter (Launchpad), find (mine is found in the other), run and then the upper right corner

　　　

　　　　

　　　　

　　　　

Store it on the desktop and then just complete the exit Keychain tool.

2. Apply for development certificate, publish certificate

Open the Apple Developer Center (https://developer.apple.com)

　　　

　　　　

　　　　

　　　　

　　　　

　　　　

　　　　

　　　　

3. Bundle ID of the registered project

　　　　

　　

　　

　　　　

Even if the registration is done here.

4. Adding test equipment

　　　　

　　　　

　　　　

Just fill out the next step. Get device Udid: Device connection mac open itunes

　　　　

　　　　

If you feel trouble, or conditions are not allowed to choose the way Dandelion offers (Https://www.pgyer.com/doc/view/udid)

5. Configure the Certificate

　　　　

　　　　

　　　

　　　　

There is no need to worry about choosing the wrong, you configure the development certificate, then there is only the development certificate for you to choose. To configure the publishing certificate, you only have to publish the certificate for your choice.

If you are configuring a development certificate, you will also need to set up a device in this project to add which devices to debug as a real machine

　　　　

　　　　　　

Once created, just download the profile and double-click to run it. Then exit the Web page. The certificate has been applied, and the configuration is ready. You can also debug the real machine, you can also publish. (Xcode7 does not need a developer account to debug, as long as you are in Xcode login to the Apple ID account, but the release still requires the developer account) steps:

　　　　

　　　　

　　　　

After successful landing:

　　　　

Then the Fix Issue button click on it, and the system will automatically help you debug it. (Personal understanding: The bundle ID here is best to add a suffix in the back, or you have already registered this bundle ID on the page here will be an error, or you here to register the bundle ID, your other account will have to change the bundle ID)

In fact, Xcode 7 has been able to manage certificates automatically, but sometimes there are some problems. For example, I have created a good certificate, and Xcode will re-create the certificate itself, and cannot customize the name. However, Xcode 8 is said to be a lot better. Concrete can be perfected to what extent, pending textual research.

• Release process.

Open ITunes Connect (https://itunesconnect.apple.com) login account;

　

　　　　

Do not know what to fill in, you can point question marks are Chinese tips

　　　　

After creation, enter

　　　　

Complete, Save the button on the right. Then continue:

　　　　

　　

　　　　　　

First upload the app, the latest rules are as long as the upload 5.5 inch on it, video, look at the individual, like more than 10 seconds or so, I have not uploaded, pictures, video content If the app is real, and then is the app description (description of the content to match with the app), keywords (said not to appear the name of the competition) , no research), technical Support website, marketing website (two URLs can not also use the company's website); The following sections:

It's all done and stored. Then check that there are no errors, or wrong writing. (Fill in the process, it is best to fill out some of the storage, to prevent network problems, white, especially after uploading) and then back to Xcode, open your project:

　　　　

　　

　　　　

　　

　　　　

　　　　

　　　　

　　　　

　　　　　　

Here's how to export an IPA submission:

　　　　　　

　　　　

The next few steps also choose to publish the certificate, check the publishing profile (note: If the export to the distribution site of the IPA, the published profile must be Ad-hoc, the enterprise account can also be in-house, detailed reference: Dandelion's instructions), and then select Save Path. Then open it in Xcode:

　　　　

After running, login to the developer account. Add the IPA file, next, Next, you can submit it to iTunes Connect. (Please refer to: https://www.pgyer.com/doc/view/app_upload) steps to the distribution site. The procedure is almost unknown. The speed of the submission process is related to the speed, you can close Xcode after success, back to ITunes Connect.

　　

Enter the activity. Check to see if the project is in a built state, and if it is complete, continue:

　　　　

After the build is added, the complete submission of the entire data is almost completed. Then set:

This is based on individual needs, set prices, sales range and so on. Check it out and see if there is any wrong place. No, you can click Submit in the upper right corner for approval.

Another, you can also add the app on the AppStore localization, AppStore will be based on the localization you do, to achieve different regional accounts to see your app is displayed in a localized language, if you do not localize, then the display is your AppStore primary language

　　

　　

The last is this page, or the same there is, there is no, choose to submit. Just waiting for the review. Now the new application, I personally tested 3 business days on the shelves, the update iteration of the application is 24 hours on the shelves. This specific, look at the luck.

　　

Issues encountered during the publishing process: (Continuous update)

1. Submit it and wait for the build to complete. Suddenly found that the build was not visible in the activity:

Check the mail, is not because of the permissions problem, build failed, so no build version is displayed;

iOS certificate request and release process