Publish app to AppStore whole process

To publish the first need to publish the certificate, its acquisition and installation of the basic process and the Real Machine Debug certificate consistent, about the acquisition and use of the real Machine Debug certificate can refer to this article. But now Xcode7 do not need a real Machine Debug certificate can also realize the debugging of the real machine, you can refer to this article.

To obtain a certificate, and publish the app, you need a developer account, the developer account is divided into two types of individuals and businesses, https://developer.apple.com/programs/this site registration. About applying for developer account, have time to write an article again.

Get and install the publishing certificate

Now assume that you have a developer account, in order to avoid not knowing how to install the developer certificate, or simply say:

First, enter the Https://developer.apple.com/membercenter/index.action Developer Center to log in.

Click on the module below to enter the certificate module.

After entering the display such as, you can see the app with iOS, Mac app and browser extension, when your developer account has the corresponding development rights will show the details under its plate, here we look at the iOS Apps section, four parts of the plate Certificates (certificate), Identifiers (Logo), Devices (device), Provisioning Profiles (configuration file), respectively, to see the contents of our account under the various parts, here we first point to the first certificates (certificate) to see.

If you go in, look at the left column first, or just the four parts, here you can easily choose to view, and now we are in the interface is the certificate interface we have. We look at the right part of the picture, show all the certificates you have, the first column shows you the name of the certificate definition, the second column shows the type of your certificate, including the real Machine Debug certificate and publish the certificate, and so on, "iOS development" means the real Machine debug certificate, "iOS Distribution "means to publish the certificate, the third column shows the certificate expiration time, more than this time the certificate expires, here I have created a certificate, so see four certificates, click on the first one of the real Machine Debug certificate, you can delete (cautious!) and download, as for the download of what is the use, later will say. When you first come in, the list does not have a certificate, you need to click Gash in the upper right corner to create the certificate.

After clicking the plus sign, the Certificate Type selection screen appears and we select the App Store's publishing certificate.

In the process of going down, you will need a CSR file that needs to be generated on the computer.

Click on the rocket graphics on your Mac to enter launchpad and find the Keychain Access icon, such as:

Open and click on the top left keychain to access the certificate----from the certification authority to request a certificate.

dialog box with certificate request opened after that, the purpose here is to get the keychain file we needed to create the certificate, two ways to get it, one for e-mail, and one to store it directly on your computer. If you choose to use e-mail, the above two text boxes need to fill in the E-mail box is to receive the mailbox, the two mailboxes must be filled in the same, in order to facilitate or always choose to save to disk, but the e-mail address is to be filled out and consistent, but no need to fill in anyway, as long as the same, Save to disk Click to continue will want you to choose the location of storage, be sure to let yourself find.

When successful, you get a certificatesigningrequest file, which is often seen as a CSR file.

After the keychain CSR file is created, you can go back to the website interface, select the Keychain profile upload that we just created, click Generate to create the success, and then click Download to download it to our computer, so we get this real Machine Debug certificate cer file, Then, double-click the file, you must double-click to install the certificate into the keychain, otherwise the use will be problematic, you double-click to see it flashed a bit, in the keychain can find this file.

At this point, we have completed the first step, note that this is only the first step Oh, do not think to get the certificate can be all right, but also early, have to say is really ... It's too much trouble. OK, go on with our work.

Now let's go to the identifiers section and create an app ID for our project, which is the engineering logo, or the project signature. Click on the app IDs in the identifiers section on the left side of the interface to see the list of flags you've created and click the plus sign to create a new logo.

You need to fill in the name to be used to find this logo, and then fill in app ID suffix app ID, which is the project ID, there are two kinds of logo, one is explicit App ID fixed logo, corresponding to a project, if there are multiple projects, You can also select the wildcard App ID wide-area identifier, which can correspond to multiple projects. How to fill in the logo It also gives an example.

After submission we get a project logo, this step can be finished, it is simple, go to the next step.

Now it's finally the last step to get the certificate! The content we created earlier is fragmented and unrelated, and the final step is to fuse the certificate, the engineering identity, so that it can be managed uniformly, so for the last part: Provisioning Profiles configuration file, My understanding is to put the above information together with a specific project, so as to facilitate management, if there is not the right place to give advice ~
As with the above steps, click on the PP section of all, click the plus sign in the upper right corner to create a new PP configuration file, also not worthy of the picture lazy ...
At the time of creation, select the first debugging part of the real-computer iOS App distuibution The real Machine debug file, select the app ID, the certificate, the last name, download to local.

As with the previously downloaded certificate file, double-click the file to install it in Xcode for normal use, and see a flash to indicate that it is installed.
At this point, our preparation work is basically completed, the next step is to go to Xcode set up a certificate.

Set up a publishing certificate

The first step: under the supporting files of the project, locate the. plist file, and then find the bundle identifier line in the list on the right, set to match the project logo we just created;
The second step: Click on the project name (top blue), the middle list select the project name under targets, find the code Signing section in the list on the right, find the provisioning profile Select the PP configuration file we just created and installed, or code Signing section, locate the Code Signing identity Line, the subordinate of the four all changed to we create and download the certificate CER file, note, not pp file;
Step three: Under Project in the Middle list, select the project with the same name and make the same changes as the second step.

So, ready to go, you can apply for the release.

Submit to App Store

The front is the prep phase, and the real release is now only the beginning.

Now go back to the developer center Https://developer.apple.com/membercenter/index.action we just had.

Just now we are entering the certificate module, and we are entering the itunes module, which is the App Store module:

Here we go to the "My Apps" section, and other analytics sections will show some statistics about the app after it's published.

After entering, the upper left corner has a + sign, click on it to create a new app

Then fill in this simple information interface, where the package ID is the bundle Id,sku own a more unique name, all the content to be filled out can click the question mark to view the explanation, now all in the culture, very convenient.

After the creation of the app information to fill the interface, there are several tab tags, where the "App Store" tab is displayed in the App Store, the "Activity" tab is submitted from Xcode file, then you will see.

Almost all the information under the "APP Store" tab must be filled in carefully. Also each place has a question mark button to see the explanations, explaining a few more to note:

• Each size of the app needs to fill in, as long as your app has support, you have to provide, you can directly in the various size of the simulator run, press Command+s, the picture will be saved on the desktop, the size is just right, you can directly submit it. Pictures can be dragged in the order of movement, you can also click on the upper left corner of the picture to remove the picture, up to five photos
• Description is the description displayed in the App Store
• The URL will allow users to click through the link in the App Store.
• The copyright information will eventually appear at the bottom of the App Store app information, with no more formatting requirements, and it looks like a formal point.
• Grading information will automatically calculate the grading after selecting all the items.
• Audit information needs to fill in, need to log in use, be sure to provide a test account to the auditor log in use, what the situation should try to explain in the notes, to prevent rejection.
• When filling in the information, please feel free to click on the storage button in the upper right corner to store the information you have filled.

Once this information is completed, you can go to Xcode to submit the IPA file.
First, the running device in Xcode must be an iOS device or a real machine, not an emulator, or it will fail to pack.

Then click Product-->archive in the menu bar to package the project. After packing, it will enter a submission interface (this interface can be accessed from the menu bar later Window-->organizer). The interface to the left will show your app list, the middle shows you an app under each version of the IPA package, just packed will also appear here, now click on the right of the submit button:


This will let you choose to submit to the account, select your developer account, and then you can upload, upload takes some time, there may be no progress for some time, no matter patience, his progress is not very accurate, and the speed is also related.
After uploading, you can go back to the website just filled in the app information, go to the "Activities" tab, in "All builds" can see a package was uploaded up. Apple will simply review the package for a while. Nothing unexpected will change from gray to a color of apparent success. If it fails, it will show a red exclamation mark, which is going to go to your registered mailbox to see what is the problem and will receive the message. Resolve issue re-upload until successful.
If it succeeds, we go back to the App Store tab and in the "Build" area you will be able to select the version you just uploaded. Now that all your work is ready, you can click submit for review in the upper-right corner. If there is any information to fill out the incorrect, will prompt you, fill up the good. The submission will also let you choose whether some encryption or the like, choose the right can wait for review.
General audit takes a week, you can occasionally log on to the site to see the progress, if you have any message mailbox will also receive mail. If it fails, Apple will inform you of the reason for the rejection and can communicate and modify the submission.


Release the new version in addition to the first review, the subsequent update is also very simple, or in the itunes Connect section, under the "App Store" tab, click the Add version, and then the basic process is similar to the above, to fill in the information at the top of a new feature fill box. Just remember to replace the debug certificate and publish the certificate between development and release ~

Publish app to AppStore whole process