iOS certificate and configuration file settings

This article summarizes the iOS certificate (certificate) and configuration file (provisioning profile) in conjunction with the author's work experience.

1. Release process

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M02/7E/E6/wKioL1cMnn7AVMhsAABhociPLMo999.png "title=" 1_ Administration_tasks_2x.png "alt=" Wkiol1cmnn7avmhsaabhociplmo999.png "/>

Both the certificate and the associated configuration file are used during the development and release process. The configuration of the specification ensures that your application will not be rejected or affected by the certificate issue after it has been listed.

2. Code signing (signing)

Only applications that are signed by code can guarantee that their source is reliable, and that the code is intact and not changed. The code signature is composed of a signature (signing identity) and a configuration file (provisioning profile).

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/7E/E6/wKioL1cMoMLxPkK-AAQg3aDQSYI611.png "title=" 2_ Viewdetails_2x.png "alt=" Wkiol1cmomlxpkk-aaqg3adqsyi611.png "/>

Signature Identification (consisting of a pair of public private keys generated by the Apple-provided algorithm), Xcode creates the app with your signature.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/7E/E6/wKioL1cMnf6Tmjf7AADmhn6oAWE889.png "title=" Certificates_2x.png "alt=" Wkiol1cmnf6tmjf7aadmhn6oawe889.png "/>

, Juan Chavez uploads his public key to Apple to generate his development/product environment Certificate (certificates), the computer-generated application that holds his private key to match the success, thus guaranteeing the first condition of the compilation/submission success. Compiling the. CER certificate required to install the development environment on the native computer, the publication needs to be held in Apple's official valid product. CER certificate.

The second condition to ensure successful compilation/commit is the configuration file (provisioning profile). This file is generated in the background of Apple developer, about how to generate, refer to 3.2.

3. Certificates, configuration Files

If you happen to have background admin access to the app, you'll be able to see the certificates, IDs & Profiles menu in the Apple Developer backend. In this directory, there are certificates, Identifiers, Devices & Provisioning profiles Four levels of two menu. Their relationship is represented by a picture:

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/7E/E9/wKiom1cMpUXyeANTAAETH44OykQ017.png "title=" 19100011-967bd3326acb49db98412f0c70d7fe41.png "alt=" Wkiom1cmpuxyeantaaeth44oykq017.png "/>

(1) certificate (certificates)

Certificates are used for application signing, and certificates contain two sets of environments for development (development) and product (production).

650) this.width=650; "style=" WIDTH:513.797PX; "src=" http://s5.51cto.com/wyfs02/M01/7E/E6/ Wkiol1cmmcoj531zaaidw9xm7lw024.png "title=" C0ab984a-7835-4d83-8dab-27cffe767e61.png "alt=" Wkiol1cmmcoj531zaaidw9xm7lw024.png "/>

In general, the development environment will create a developer certificate for each developer, and the release version will have a common product certificate. In addition, if the app contains other invocation services, such as notifications (app push notification Service), the corresponding certificate is generated separately.

The steps to generate the certificate are no longer exhausted and can be completed by booting.

(2) configuration file (Provisioning Profiles)

With respect to certificates (certificates), Configuration files (provisioning profiles) also have development/product two sets.

Configuration files for development (IOS development)

This file is intended primarily for developers to test on sandboxed phones, so when creating the profile, you need to tick the relevant developer certificate (which developer compiled packages have permission to run), and the associated sandboxed mobile device (the device is registered in devices).

Configuration files for publishing (IOS distribution)

This file is used to upload packages to TestFlight and the Apple App Store. Therefore, when you create the profile, you need to tick the certificate used for publishing.

It is important to note that once any certificate fails, its associated configuration file becomes invalid, and the new certificate can be regenerated, but only the corresponding configuration file needs to be edited and its associated certificate refreshed.

Develop/Publish switch certificates and configuration files in Xcode:

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/7E/E6/wKioL1cMpWqDlCyaAAK8fZi0zf4708.png "title=" 12_ Buildsettings_2x.png "alt=" Wkiol1cmpwqdlcyaaak8fzi0zf4708.png "/>

4. p12 file

As shown above, the certificate (certificates) is a credential that verifies that the app is valid. But the certificate is installed directly in the Mac system, how to let it import into other systems, so that the app ID to request other Apple services (such as notification, etc.)?

At this point, you need to use the. p12 file. The. p12 file is a file that is processed by special formatting and encryption that contains the application certificate. It is exported in the following ways:

650) this.width=650; "style=" Float:none; "src=" http://s5.51cto.com/wyfs02/M00/7E/E7/ Wkiol1cmql-ywsxcaahyw0od74e170.png "title=" 1.png "alt=" Wkiol1cmql-ywsxcaahyw0od74e170.png "/>

650) this.width=650; "style=" Float:none; "src=" http://s5.51cto.com/wyfs02/M01/7E/EA/ Wkiom1cmqarbeitmaablfuk62yy831.png "title=" 2.png "alt=" Wkiom1cmqarbeitmaablfuk62yy831.png "/>

650) this.width=650; "style=" Float:none; "src=" Http://s5.51cto.com/wyfs02/M01/7E/EA/wKiom1cMqauSq-s_ Aabta22xaoc993.png "title=" 3.png "alt=" Wkiom1cmqausq-s_aabta22xaoc993.png "/>

650) this.width=650; "style=" Float:none; "src=" http://s1.51cto.com/wyfs02/M01/7E/E7/ Wkiol1cmqmcqy4xiaabqo8zsozu080.png "title=" 4.png "alt=" Wkiol1cmqmcqy4xiaabqo8zsozu080.png "/>

650) this.width=650; "style=" Float:none; "src=" http://s4.51cto.com/wyfs02/M01/7E/E7/ Wkiol1cmqmcdryeyaaa-mepekn4755.png "title=" 5.png "alt=" Wkiol1cmqmcdryeyaaa-mepekn4755.png "/>

In many mobile application proxy platforms, both use the. P12 method to allow the user to submit their application's P12 file to the proxy platform, which is used by the platform to relay related requests/responses.

In addition, because the certificate used for publishing has and can only have one active state, the certificate's build can contain only one private key of the developer ID. If you need more than one person in your team to assume the functionality of the release, you can now think of:

1. Create a developer ID dedicated to the release version and publish the certificate with its bindings

2. Export the. p12 file for the developer ID certificate and share it with the relevant publisher

3. When a Publisher releases a release, it is packaged with a public developer ID

If the reader has a better way, please enlighten, thank you.

Hope this article can bring you help!

Related information:

About APP Distribution Workflows

Maintaining Your Signing identities and certificates

Maintaining Identifiers, Devices, and Profiles

This article is from "Leo's Technical Diary" blog, please be sure to keep this source http://shskey.blog.51cto.com/8310114/1763007

iOS certificate and configuration file settings