The most attentive iOS app in history "Go"

Turn: http://www.jianshu.com/p/16fa56eacb5e Preface

Numb up, hey! See so many tutorials on the internet, still in my beloved love fart on shelves encountered various J8 problems, the biggest problem is: Xcode certificate what, Provisioning profile what, Debug what, Production and distribution What disorderly 78 bad all confused me, online many tutorials are good old (although the idea is the same, but not enough detail), so I intend to put my this year has shelves of dry goods (, introduction address) on the shelves of arduous process write down, one can let oneself later on the shelves of the app can reduce a bit of detours, Second, we can give you a reference.

Pre-heating before shelves

Log in to your developer account first (sign up for your iOS developer account in advance, assuming you already have an iOS developer account) and go to this page:
Https://developer.apple.com/account/overview.action

Since I'm submitting an iOS Apps, I'm going to the leftmost column:

At first, looking at these "certificates, Identifiers, Devices, Provisioning Profiles", feel nothing, but to the actual use up, special I will circle. Let's explain what these few ghosts are, and uncover their truth.

• Certificates: certificate, commonly used certificate type has 4 kinds: Real Machine Debug Certificate, push Debug certificate, publish certificate, push production certificate.

• Identifiers:app ID, which matches the project's Bundle Identifier (which is the red arrow pointing to the <font color= "Red" >me.angelen.Ganker</font>), as shown in:

  
  

• App IDs that need to support features such as push, Game Center, cannot contain wildcards * (that is, when you create a new app ID, you select the suffix of the app id).

  
  

• The Devices:ios device needs to contain the device's Udid to be installed when it is debugged and Adhoc released.

• Provisioning Profiles: Configuration file (profile), different types of developer accounts include development, adhoc both profiles, the difference is that the individual, the company developer account has published to the AppStore profile, The Enterprise Developer account is the profile published within the InHouse enterprise.

See me again disorderly, not afraid, slowly to explain.

Start on the shelves of the road 1. Apply App ID

Select Identifiers App IDs, and click the "+" sign in the upper right corner to fill in the information to apply for the app ID.

Note: The name of this app ID description is used to describe your app ID, this random, no restrictions, preferably the project name, so that you can easily identify (do not allow Chinese AH).

Note: App ID Suffix, which is the suffix of your app ID, this needs to be carefully. Because this content and your program directly related, many places to use, preferably com.yourcompany.yourappname format, I use the project Bundle Identifier (anyway this is the most insured, the above mentioned what is the bundle Identifier).

Note: APP services, the default will choose 2 items, can not be modified, only need to choose the service you want to do, do not know where to see that it is necessary to choose the push, otherwise there is no way to modify, but I test it can be modified. If you do not trust the program?? You can select it and then click Continue.

Confirm that there is no mistake. Click Submit and click Done to complete the creation of the App ID, as shown in:

2. Create a certificate (Certificates) 2.1 Create a certificate request file

Create a certificate request file first. The app on your MAC finds "keychain access", such as this icon:

When open, select Keychain Access-Certificate assistant-Request a certificate from the certification authority as shown in:

Fill in the certificate information and save the certificate.

Note: User email address to fill in the developer's mail, the common name is the name of the key in the certificate, CA e-mail address is not required.
Click "Continue" and select the location where you store the certificate to generate the certificate request file as shown in:

2.2 Starting a certificate creation

Certificates have two major classes, development certificates (development, also known as debug certificates), and publishing Certificates (Production).

Commonly used in the following categories:

①ios APP Development: True Machine Debug Certificate.

②apple Push Notification service SSL (Sandbox): Push the Debug certificate, the App that directly debugs to the device with Xcode needs to debug the certificate push notification.

③app Store and ad hoc: publish certificates, App Store, in-house (previously there is this, but I do not see, first, regardless of), Ad Hoc publishing methods require this certificate to sign.

④apple Push Notification service SSL (Sandbox & Production): Push a formal certificate, AppStore, in-house, and adhoc all require a formal push to send a certificate push notification.

Note: These types of certificates are created with the need to upload a CSR file (the Certificatesigningrequest.certsigningrequest file that you just created).

Publishing certificates and developer certificates requires two operations, created separately, developer certificates for real-world debugging, and publishing certificates for submission to the APP Store.
For example, tick IOS App development, click Continue, it will prompt you to need a CSR file.

Wit, as I have already created, is the Certificatesigningrequest.certsigningrequest file mentioned above.
OK, keep Continue.

Select the CSR file and click Generate.

You can download it to your Mac and find a place to put it.
Similarly, the App Store and Ad Hoc are the same way to create.

Oops, also, know that I have created IOS App development, to turn me gray can not click.
The last step is the same as creating IOS App development:

However, the name of the certificate development The IOS APP is a bit different. One is iOS Development:microlen Yan (my) and the other is iOS distribution:y. S.: Technology Co., Ltd. (company). Also downloaded to the computer, you have the following two files on your MAC:

You can also see in the Developer Center:

Both certificates are valid for 1 years.
Double-click the two CER certificate file to install both certificates. (If not installed, you can drag the certificate file directly into the list of keychain access)
This should be the case when the installation is complete:

3. Create configuration file (Profiles provisioning profile)

Click the "+" sign in the top right corner to create the Provisioning profile for development and the Provisioning profile published to the APP Store:

Take iOS App development as an example.

Select the app ID you've created before, and next:

Select the certificate, which is also the certificate you just created. Continue to the next step:

Note: The development of Provisioning profile requires real machine debugging, so here to bind one or more of the real machine, here I was added before the real machine, so can be directly checked; If not, you need to copy the UUID of the real machine in this Add (method: Use mobile Safari Access Http://fir.im/udid). There is, in the release of Provisioning profile, is not this step, the truth we all understand! (Do not know and do not ask Niang)
OK, after the tick, direct Continue:

After filling in the profile Name, click Generate to generate:

Download it down, Sao year! Then go to create a release Provisioning profile, the steps are similar to the above.
There is a little bit of a difference when choosing a certificate:

After the same completion, download it down. Now there are two more Provisioning profiles:

Double-click to add to Xcode, so that when the real machine debugging or publishing, you can have a different Provisioning profile corresponding to each other. However, actually can not download save, because can be downloaded in Xcode (the specific operation below, I also later heard, forgive me not to read well).

4. Project configuration (in Xcode)

In Xcode, select the Xcode--preference following interface and select the Accounts tab:

Select the Admin, then click View Details ...

Here you can download your Provisioning profile (Xcode can do the right thing).
Configure the Provisioning profile property of project for the following projects:

Then use the real machine package: product--archive (if not the real machine, as if Archive this menu item is gray can not click)

For the sake of insurance, let Apple audit smoothly, first click "Validate ..." to verify:

Validation verifies that the following problem has occurred:

It seems to be a problem with this itunes connect, so go to itunes connect to register a message for the app.

https://itunesconnect.apple.com/WebObjects/iTunesConnect.woa/ra/ng/
I've tried many times to get in, Apple, the pit daddy. Click on "My App" to create a new app.

After you click Create

Fill out the appropriate information and click "1.0 ready to submit".
The information to be filled in include: Version information, app comprehensive information, Game Center (I do not use it temporarily), app audit information, additional information, fill it up after the storage (recommended every time you fill the storage, ITunes Connect often network to do aircraft).
Yes, there is also a "build version", which packages the code into an IPA file. After the build (build method below) is complete, come back to this iTunes Connect and fill out the build version

There are two ways to build a version, one is to use Xcode, and the other is to download a software called application Loader:

• Xcode Build Version:
  With the real machine packaging: Product--archive after entering the following page (or already Archive can be entered through Window--organizer):
  
  

See the Blue background button No, Upload to App Store ... Follow the instructions later.

I recommend using the application Loader.

• Application Loader Build Version:
  For example, click "Export ..." to export an IPA file (in fact this time you can click "Validate ...", but I am lazy).
  Then open application Loader This software and double click "Deliver Your Application":
  
  

It will verify your app, and if the upload is complete without error, then 10 minutes or so after Apple has finished processing this version, you can go to the "build" in ITunes connect to select the version just uploaded.
Fill it out like this:

All right, the information is complete. Submit your review at the top right corner of ITunes Connect! I wish you a smooth app on shelves!

Wen/angelen (author of Jane's book)
Original link: http://www.jianshu.com/p/16fa56eacb5e
Copyright belongs to the author, please contact the author to obtain authorization, and Mark "book author".

The most attentive iOS app in history "Go"