XCode8 true Machine test packaging to make it easier to publish tests

ios-'s most complete test tutorial for true machinesI just use it as a note, please don't spray, thank you

I love you not because the who you are,but because the Who I am

Want to go to the shelves of students see: "ios-the most full app on the shelves" because recently updated Xcode 8, the certificate was created the same, just in Xcode 8 settings have some changes, I will add below, if you have any questions, please contact me.

Note You can also set up a certificate in the sign of build Setting, but there is a hassle, it's a good idea to set up a certificate in general, and you can see where the error is.
444444444.png prepare Developer Account

Since the Xcode7 out, the general real machine testing does not require a developer account, you do not need to see this tutorial, only the app has "push" and other functions, to the real machine test must be a developer account and set the certificate. Apple just lets you experience its basic function, to go deep or to spend money. Projects to be tested real-machine test step One, create App ID II, create a certificate request file (CSR file) iii. Create a developer certificate (CER) (development, test-Develope Certificate) based on CSR Iv. Add Equipment (Devices) v. Create Provisioning Profiles profile (pp file) based on devices six, set Xcode and then true machine debugging focus on using P12 files to make multiple Mac true machine debugging (or Publishing) "Focus" one, create app id< /c6> 1. Open the Apple Developer Network and click "Account" to sign in to the Member center.


2. Fill in the information to create the app ID

Click + Create ID

First option: The explicit app ID corresponds to the bundle identifier in the project
If you plan to add game Center to your application, or buy it in your application, do data protection, use icloud, or want to give your application a unique profile, you must apply for the explicit app ID.

The second option: The generic app ID can be used in all apps that don't need an explicit ID
The Real machine debugging certificate that Taobao sells is this


Second, create a certificate request file (CSR file)

To create a CSR file look at the 2nd of the ios-app tutorial. Third, create a developer certificate (CER) based on CSR

1, find certificates, click All, and then click the top right corner + number

2, click the iOS App developement option in developement

3. Click Continue

4. Click Continue

5. Click Choose File. Select the created certificate request file: Certificatesigningrequest.certsigningrequest file, click Generate

6. Click Download to download the created release certificate (CER suffix file), and then click Done, the certificate you created will be stored in the account number

7. double-click Install. If it is not installed, you can drag the certificate file directly to the list of keychain access Four, add a device

1, Click + Add equipment to the developer account, for the production of PP file preparation

Name: The description of the device can be filled with your memory.
UDID: Marking of equipment

2. Get UUID (here is a way to get UUID)
Insert your iphone into your computer, turn on itunes, and then follow the instructions as shown

3, fill in the UUID on the OK five, according to devices create provisioning Profiles configuration file (pp file)

1, Find provisioning Profiles, click All, then click the top right corner + number

2, choose iOS App developement, click Continue

3, in the app ID this option bar to find you just created: app IDs (Bundle ID) type of suit, click Continue

4. Select the release certificate you just created (or the certificate that generated the P12 file), click Continue

5. Select Equipment

Note: Wildcard format of the certificate does not push, passcard and other services, the application of prudent choice. Because the developer Certificate of PP certificate requires the real machine debugging, so we need to bind the real machine, here because some devices have been added, so this can be directly selected add, if not, you need to copy the Udid of the real machine to add here. In the published PP file, there is no such step.

6, in the Profile Name column to enter a name (this is the name of the PP file, you can easily input, here I use the project name, easy to separate), and then click Generate

7, then click to download, download it down

Double-click to add to the Xcode, so that when the real machine debugging or publishing, you can have different PP certificate and its corresponding. Actually can not download save Six, set Xcode true machine debugging

1, set the bundle ID and the application of the AppID consistent

2, set the debug CER certificate
3, the Configuration Certificate description file (pp file)

4, select the real machine for real machine debugging use P12 file to make multiple Mac debug (or publish) "Focus"

1, why to use the P12 file

When we develop applications with more than three Mac devices, to apply for a new certificate, if in our certificate, contains 3 issued certificates, 2 development certificates, you can find that no longer apply for the development of certificates and certificates issued (generally in our certificate interface should have only one development certificate, a certificate issued, There is no need to generate so many certificates, and the certificates are typically not added again until they expire. ）

At this point, then click on "+", you will find that the development and release of the certificate can not be added to the development of certificates and certificates issued:

2, P12 file can solve what problems
We have 2 solutions to the problem of not adding a certificate

The first method-"revoke" (not recommended):

Put the previous certificate "revoke" off,
Then regenerate a new certificate.
This method is OK, but will cause the corresponding provisioningprofiles (pp file) invalidation, this is a small problem. But it is a waste of time to reapply for a certificate or even to describe a document, so it is not advocated.

The second Method-". P12" (recommended):

Each of our certificates can generate a. p12 file, which is an encrypted file that can be used by all MAC devices if you know its password, so that the device does not need to reapply for development and release certificates on the Apple Developer Web site.

3, how the P12 file is used

Note: The general. p12 file is for others to use, this machine must already have a certificate with a secret key to generate. p12 file

Export a certificate with a private key (here I choose to debug a certificate that is debugging a CER certificate, in fact, it can be a certificate, but it is not for debugging but for shelves). Then click Export

Fill in the name and storage location, click Save

Fill in the password for the P12 file certificate, point "OK"

Then generate the P12 file

In fact, P12 file is not only the real machine test when used, shelves will also use, P12 file usage, debugging and shelves are the same. The easiest way to understand this is to use the P12 file as a CER file, debug it as a CER, and release the CER when it is posted.

Using
Debugging: is to take the third step of the tutorial to create debugging certificate omitted, replace it with P12 file can be
shelves: the "ios-most of the app shelves tutorial" The third step through the issuance of the certificate omitted, replace it with P12 file.