IOS certificate sharing

All those who have performed IOS testing know that the IOS certificate is only tested on the applied machine without being processed. Sometimes we may need to test on different machines for convenience. Then you need to process the certificate. The solution is as follows:

Some of the readers mentioned previously contacted me privately and said they were a little confused. Then I will discuss the solution again. Add

On the computer where the certificate is generated, open the key string and select your certificate.

After you select the key, the certificate will appear on the right side. Right-click the certificate and select export XXX ''certificate.

Fill in the password (remember ). Generate a new certificate named certificate. p12.

Copy the certificate to the computer you want to add. Double-click the certificate and enter the logon password.

Okay. Try it.

Supplementary content: (from the Internet)

I. Member Introduction
1. Certification (certificate)
Certificates are used to authenticate computer development qualifications. Each developer account has one set, which can be divided into two types:
1) Developer certification (Development Certificate)
Install on a computer and provide permissions: developers can perform real-machine testing through devices.
Copies can be generated for installation on multiple computers;
2) distribution certification (publish a Certificate)
Install iOS programs on your computer and grant you the permission to publish iOS programs: developers can create beta and release programs.
A copy cannot be generated and can only be used by the computer with the certificate configured. (The copy creation is described in the keychain below)

2. provisioning profile (authorization file)
An authorization file is an authorization file for devices such as iPod Touch, iPad, and iPhone. The file records the device's udid and the app ID of the program, even if the authorized device can install or debug the program corresponding to the app ID recorded in the authorization file of bundle identifier.
When creating the authorization file, the developer account selects the app ID (add the app ID under the developer account, single choice) and udid (add up to 100 devices under the developer account, select multiple ).
There are two types of authorization files, corresponding to the use of the corresponding certificate:
1) Developer provisioning profile (Development authorization file)
To use it on a computer with a development certificate or copy, the developer selects the authorization file to install the program to the device with the authorization file record through the computer to perform a real machine test.
Note: Make sure that the computer has the permission to debug the real machine, that is, the development certificate or copy is installed. In the development tool, the bundle identifier of the program must be consistent with the app ID of the selected authorization file; the device's udid for connection debugging is recorded in the selected authorization file.
2) distribution provisioning profile (publish authorization file)
Create a beta and release version program on the computer with the certificate publishing device (that is, the computer with the certificate configuration, only one.
The release version is the program file released to the app store. when creating the authorization file for the developer account, select the store option and the app ID, without the need to select the udid;
The test version is the program file that can be synchronized to the device by the tester before release. when creating the authorization file for the developer account, select adhoc and select app ID and udid; only the device corresponding to the selected udid can install the program created using the authorization file.
3. keychain (Development key)
If the certificate is successfully installed, the keychain will be generated under the certificate. The certificate copy mentioned above is exported by the computer where the certificate is configured (that is. p12 file) install it on another machine, so that other machines can obtain the certificate permissions. Developer certification can make a copy of keychain and distribute it to other computers for installation so that it can perform real machine testing.
Note: Distribution certification is only available on the computer where the certificate is configured. Therefore, even if the exported keychain is installed on another computer, it is impossible for other computers to have the certificate permission.