Apple all common certificates, appid,provisioning profiles configuration instructions and production graphics tutorial (fine)

   Original address: http://blog.csdn.net/holydancer/article/details/9219333

Overview:

Apple's certificate complex lock, production management is quite troublesome, today decided to reset a game project all the certificates, did so many times or feel very tangled, simply directly recorded down, you and I he check all convenient;

First of all, to describe the location of the certificate, the role, so that in the production of the mind has a spectrum, the whole process of grasping will be accurate;

1, developer certificate (divided into the development and release of two, the type of iOS Development,ios distribution), this is the most basic, whether it is the real machine debugging, or upload to AppStore are required, is a base certificate, used to prove their developer identity;

2, AppID, this is the independent identity of each application, in the settings can be configured to configure the app's permissions, such as whether to use the Passbook,gamecenter, and the more common push service, if the push service is selected, Then you can create a push certificate mentioned in 3rd below, so, in all and push related configuration, the first thing to do is to first open the support push service AppID;

3, push the certificate (divided into two types of development and release, the type is APNs development Ios,apns distribution iOS), the certificate in the AppID configuration to create a build, and the developer certificate, installed on the development computer;

4, Provisioning Profiles, this thing is very apple features a thing, I generally called the PP file, the file will be AppID, developer certificate, hardware device binding to one, in the developer Center is configured to add to Xcode, You can also directly connect to the developer center in Xcode, the real machine debugging needs to add the udid of the real machine in the PP file, is the real machine debugging and must rack necessary treasures;

Usually our production process is generally based on the above sequence, first use the developer account to login to the developer Center, create a developer certificate, AppID, in the AppID to open the push service, in the Open Push service option below to create a push certificate (server-side push certificate see below), Then in the PP file to bind all the certificate ID, add debugging real machine, etc.;

The following procedures are described:

1, the developer certificate production, first login to the developer center, find the Certificate configuration section, poke into the certificate, will show the following interface, click on the upper right corner of the plus

The following interface appears, the operation is repeated two times, respectively, the development of test certificates and publish certificates, the development of test certificates for real-machine debugging, publishing certificates for submission to AppStore, we take the development of test certificates, for example, the first red box to select the content;
Then next, you will be prompted to create a CSR file, which is the certificate signing request file, there will be very detailed instructions, if the English is not very good, you can refer to;

Then save the CSR file to a place;

Note: The CSR file is made as often as possible for each certificate, separating common names, because the common name is the name of the key in the certificate;

Then submit the CSR file in the developer center;

Upon submission, a CER certificate is generated, valid for one year;

Use the same method to configure the distribution publishing certificate, download save, double-click Install, in the key string login certificate can be viewed, where the name of the private key is the CSR request file in the common name;

2, the above developer certificate configuration is complete, the following we configure AppID and push certificate, select AppID in the left column, tick the push option on the right, add push function for the corresponding app for the AppID, see the button to create the certificate, respectively, to develop the certificate and publish the certificate. The following process is the same as the above 1 to create a certificate, is to establish a certificate request file, and then submit the build on the line, it should be noted that although the left column in the certificate bar can also be directly created a push certificate, but it is recommended in AppID, check the push service is created here, This avoids the fact that push is not available due to forgetting to open the push service;

After the certificate is created, download and save, double click to install;

3. Finally, we will make the PP file

This process is done two times, respectively, to create a development test with the PP file and publish the PP file, the former for the real machine test, the latter for the submission of the release; Ad hoc format is generally used for enterprise accounts, where we ignore;

Submit after selection

will automatically detect the matching AppID, in addition to the drop-down item can also choose the wildcard format, the format is automatically generated, using the * wildcard, for batch, no push, passcard and other services applications; We select the AppID we just created, and then select the certificate;

Continue, here is a difference, because the development of PP file test version needs to debug the real machine, so we need to bind the real machine, here because I added some devices, so here can be directly selected to add, if not, you need to copy the Udid of the real machine here to add, in the release of the PP file, There is no such a step;

After the input of a PP file name, and then generate, download and save, double-click to add to the Xcode library, so in the real-time debugging or publishing, you can have a different PP file and its corresponding;

The effects added to Xcode are as follows:

So far, client development and shelves required certificate file configuration has been equipped, the sky is late, tomorrow to configure the service side of the push certificate used, then another chapter, the iOS bizarre push process also smoothed a smooth, originally wanted to write a piece of, did not expect the whole so long, work home black go!

(go) All common Apple certificates, appid,provisioning profiles configuration instructions and production graphics (fine)