IOS app publishing to App Store tutorial

IOS app publishing to App Store tutorial

To publish a certificate, you must first publish the certificate. The basic process for obtaining and installing the certificate is the same as that for debugging a real machine. Now Xcode7 can debug a real machine without a real machine debugging certificate.

To obtain a certificate and publish an app, you need a developer account. The developer account can be divided into two types: individual and Enterprise. You can register at https://developer.apple.com/programs/this website. You have time to write another article about applying for a developer account.

Obtain and install the publishing Certificate

Now we assume that you already have a developer account. To avoid having to know how to install the developer certificate, let's simply say:

First, go to https://developer.apple.com/membercenter/index.actiondeveloper center.

Click the following module to enter the certificate module.

 

As shown in the following figure, you can see ios apps, mac apps, and browser extensions. When your developer account has corresponding development permissions, details are displayed under the section, here, let's take a look at the ios Apps section, which contains four parts: Certificates (Certificates), Identifiers (LOGOs), Devices (Devices), and Provisioning Profiles (configuration files ), click here to view the existing content of each part of our account. Here we will first click the first Certificates (certificate) to see it.

 

After entering the page, for example, check the left column first or the four parts just now. You can easily select and view them here. Now we are on the certificate interface. The right part of the figure shows all the certificates you have. The first column of the three columns shows the name you have defined for the certificate, and the second column shows the type of your certificate, this includes the real machine debugging certificate and publishing certificate. "iOS Development" indicates the real machine debugging certificate, "iOS Distribution" indicates the publishing certificate, and the third column shows the expiration time of the certificate, after this time, the certificate becomes invalid. Here I have created a certificate, so I can see four certificates. Click the first real machine to debug the certificate and delete it (Exercise caution !) And download, as to what is the purpose of the download, will be discussed later. When you first come in, the list does not have a certificate. here you need to click the plus sign in the upper right corner to create a certificate.

 

Click the plus sign to display the certificate type selection interface. We select the publishing Certificate of App Store.

 

In the process of going down, a CSR file is required, which needs to be generated on the computer.

Click the rocket chart on the mac to enter Launchpad and find the key string access icon, for example:

Click the key string in the upper left corner to access --> certificate master --> request the certificate from the certificate authority.

 

The certificate request dialog box appears. The purpose of this dialog box is to obtain the key string file we just needed when creating the certificate. There are two ways to obtain the key string file, one is by email, one is directly stored on a computer. If you choose to use email, the two text boxes that need to be filled in the email are the ones you receive, and these two mailboxes must be filled in the same; for convenience, you can always choose to store them to the disk, however, you still need to enter the same email address, but you do not need to enter the address at will. If you store the email address to the disk and click Continue, you will have to choose the storage location, make sure you can find it.

 

After successful execution, a CertificateSigningRequest file is obtained, which is a CSR file that is often seen.

After the CSR file is created, you can go back to the website interface and select the newly created key string configuration file to upload. Click Generate to create the file, then click Download to Download it to our computer, so that we can get the certificate cer file for debugging on this real machine, and then double-click the file, you must double-click to install the certificate to the key string. Otherwise, the certificate may be used incorrectly. You can double-click the certificate to see it flashing, this file can be found in the key string.

At this point, we have completed the first step. Note that this is only the first step. Don't think that you can get the certificate to complete all the work. It's too early. You have to say it's too much trouble. Okay, continue our work.

Now let's go to the Identifiers section and create an app ID for our project, that is, the Project logo or project signature. Click App IDs in the Identifiers section on the left side of the page. The list of created logos is displayed on the right side. Click the plus sign to create a new flag.

 

During creation, you need to enter the Name to facilitate subsequent discovery of this flag, and then fill in the App ID in App ID Suffix, that is, the Project ID. There are two types of IDS, one is the fixed identification of the Explicit App ID, which corresponds to a project. If there are multiple projects, you can also select the Wildcard App ID wide area identification, which can correspond to multiple projects. It also provides an example.

After the submission, we get the ID of a project. This step can be completed. It's easy to go to the next step.

Now the last step to obtain the certificate is reached! The content we created previously is fragmented and not associated with each other. The last step is to combine the certificate and project identity so that they can be managed in a unified manner, so for the last part: Provisioning Profiles configuration file, my understanding is to combine the above information with a specific project, so as to facilitate management, if something is wrong, please advise ~
As in the preceding steps, click All in the PP section and click the plus sign in the upper right corner to create a new PP configuration file...
Select the debugging file of the iOS App Distuibution real machine in the first debugging part, select the app ID and certificate, and finally name the file and download it to the local device.

Like the downloaded certificate file, double-click the file to install it in Xcode for normal use. If you see it, it indicates that it is installed.
At this point, our preparation is complete, and the next step is to set the Certificate in Xcode.

Set certificate publishing

Step 1: Find the. plist file under Supporting Files of the project, find the Bundle identifier line in the list on the right, and set it to the same as the Project ID we just created;
Step 2: Click the project name (blue at the top), select the project file with the same name under TARGETS in the intermediate list, and find the Code Signing section in the list on the right, find the Provisioning Profile and select the PP configuration file we just created and installed, or in the Code Signing section, find the Code Signing Identity line, change all the four subordinate certificates to the certificate cer file we created and downloaded. Note that it is not a PP file;
Step 3: select a PROJECT file with the same name under the PROJECT in the intermediate list to make the same changes as step 2.

After the preparation is complete, you can apply for release.

Submit to App Store

The previous steps are in the preparation phase. The real release is now in progress.

Now, go back to the Developer Center https://developer.apple.com/membercenter/index.action.

We just entered the certificate module, and now we enter the iTunes module, that is, the App Store module:

Here we go to the "My App" section. Other analysis sections will see some app statistics after release.

After entering, there is a plus sign in the upper left corner. Click it to create an App.

Then fill in this simple information interface, where the Set ID is the Bundle ID. the SKU just needs a unique name. You can click the question mark to view the explanation of all the content to be filled in, now it's quite convenient to learn about Chinese culture.

After the app information is created, enter the App information filling interface. There are several tab labels. The "App Store" tab shows the information displayed in the app Store, the "activity" tab contains the ipa file submitted from Xcode, which will be displayed later.

Almost all information under the "App Store" tab must be filled in carefully. You can also view the explanation by clicking the question mark button in each place. For more information, see:

All apps of all sizes need to be filled in. As long as your app supports them, you must provide them. After running them directly in simulators of all sizes, press command + S and the images will be saved on the desktop, the size is suitable and can be submitted directly. You can drag the image to move the image, or click the minus sign in the upper left corner of the image to remove the image, up to five descriptions can be displayed in the App Store. The URL allows you to click the link from the App Store. The copyright information will eventually be displayed at the bottom of the App Store application information. The format does not have many requirements, and it looks like it is formal. After the grading information is selected, the grading is automatically calculated. The audit information must be properly filled in. If you need to log on to and use it, you must provide a test account for the reviewers to log on and use. If possible, describe the information in the remarks to prevent rejection. When entering information, be sure to click the storage button in the upper right corner at any time to store the filled information. After entering this information, you can submit the ipa file in Xcode. First, the running Device in Xcode must be an iOS Device or a real machine. It cannot be a simulator. Otherwise, the package fails. Click Product --> Archive in the menu bar to package the project. After the package is completed, a submit interface is displayed (you can also choose Window> Organizer from the menu bar ). The list of your apps is displayed on the left side of the page, and the ipa packages of each app version are displayed in the middle. The packaged ipa packages will also appear here. Click Submit on the right side:
At this time, you will be asked to select the submitted account, select your developer account, and then you can upload the file. It may take some time to upload, and there may be no progress for some time. It doesn't matter if you are patient, his progress bar is not very accurate, and it also has something to do with network speed. After uploading, you can go back to the website that just filled in the App information and enter the "activity" tab. In "all build versions", you can see that a package is uploaded. Apple will simply review the package for a while. If there is no accident, it will change from Gray to a color that is obviously successful soon. If it fails, a red exclamation mark will be displayed. You need to check the problem in your registered email and you will receive the email. Solve the problem and upload the file again until it is successful. If it succeeds, go back to the "App Store" tab and select the uploaded version in the "build version" area. Now, all work is ready. You can click "submit for review" in the upper right corner. If any information is incorrect, you will be prompted to complete it. When you submit the application, you will be asked to choose whether to encrypt or not. After you select it, you can wait for the review. Generally, the review takes one week. You can log on to the website from time to check the progress. If you have any email, you will receive an email. If the request fails, Apple will inform you of the reason for rejection. You can contact and modify the request to continue submission. In addition to submitting the new version for the first time, the subsequent updates are also very simple. In the iTunes Connect section, click "add version" under the "App Store" tab, and the basic process is similar to the one mentioned above, the information to be filled in contains a new function filling box at the top. I just remember to change the debugging certificate and publish the certificate between development and release ~ Now the release process is complete. If you have nothing to say, you can reply and discuss it together ~