App development process-iOS development certificate collection, app process ios collection

App development process-iOS development certificate collection, app process ios collection

I haven't summarized it for a long time. I looked back at my expired accounts and found few records. I want to summarize and record some time recently.

Since I haven't recorded it for a long time, I want to write a lot of things that are complicated. I thought about it. I 'd like to write a series of articles listing knowledge points and experiences, record the development process and experience of an application.

The main line is the process of building and developing an application. During this period, we will analyze and discuss some nodes.

 

 

This title, the reason is called "pick up the left", you can refer to my expired account (http://www.cnblogs.com/A-Long-Way-Chris/), which has recorded several development certificate articles, here just do some supplement, as preparation before formal development.

The following content mainly records the p12 certificate and pem certificate.

Add the certificate used for debugging and publishing of the real machine generated by the apple Developer Center and the certificate used for pushing to the key string (the certificate created by the current Mac device in the Developer Center ), you can see the following list (because there are multiple applications, please ignore the number of pushing certificates ):

Select the development and debugging Certificate "iPhone Developer: xxxx" to ensure that "Private Key" is not expanded. Right-click and choose "Export xxxxxx". The following interface is displayed:

You can change the name and storage location, and click "Storage". A password is required or you can choose not to enter the password (that is, no password is required for subsequent use.

The exported p12 certificate can be sent to other colleagues and added to the key string by double-clicking to facilitate debugging of projects under the same developer account.

You can perform the same operation to publish a certificate.

 

The main usage of the p12 certificate you may involve:

1. Used for development and debugging by multiple developers and multiple devices

2. Push messages through third-party platforms, such as umeng

3. Generate a pem certificate for pushing messages

 

The process for generating the pem certificate used for supplemental push:

Perform the above p12 certificate generation operation on the push certificate, for example, getting a apns-dev-cert.p12

Expand private key, right-click the key, export to get the apns-dev-key.p12

Then open the terminal program and enter the following commands in sequence:
Openssl pkcs12-clcerts-nokeys-out apns-dev-cert.pem-in apns-dev-cert.p12
Openssl pkcs12-nocerts-out apns-dev-key.pem-in apns-dev-key.p12

Enter password as required
Then enter the following command:
Cat apns-dev-cert.pem apns-dev-key.pem> apns-dev.pem

The final apns-dev.pem file that can be used for partial messaging platforms

You can perform the same operation to publish a certificate.

 

Finally, record the certificate errors encountered during the development process:
1. If the iPhone Developer: xxxx or Distribution: xxxx in the key string is prompted to expire, you need to re-edit or generate a certificate in the Developer Center, add the key string, and generate a p12 certificate to your colleagues.
2. If the prompt "Apple's security certificate expired", You need to download the new security certificate, but the next expiration there are many years: https://developer.apple.com/certificationauthority/AppleWWDRCA.cer
3. If the Xcode compilation prompts that the provisioning profile is incorrect, the configuration profile is incorrect. You need to configure the current application Debug or Release mode to correspond to the provisioning profile under the certificate.
4. When Archive is packaged and exported to ipa, the system prompts "The certificate already exists, but it is not installed locally". Most of them refer to the incorrect configuration of the ad hoc certificate. Exercise caution when clicking the "revoke" button. This operation will cause the development and release certificate to be reset.

To put it simply, as long as the p12 certificate is correctly imported, most problems are caused by provisioning profile.

There are already many summary and records of the certificate, which basically summarize the situations that often occur during the development process. The certificate is saved here first, and the next article officially starts the development process record of an App.