Today, the issue of the certificate is jammed:
On the company's computer to apply for development, publish the certificate, go home with your own computer from the Apple Developer Center on the certificate and configuration files are downloaded to the prompt, It took a long time to think of. p12 files, must be exported from the computer to apply for the certificate, imported to their own computer to use, in case later forget, redo a note, also well combed under each certificate, the role of the file.
1. Download the. cer file to another machine. is in the IDPThe one on the. 2. Private key corresponding to the certificate from the machine sending the request file (certificate request, suffix certsigningrequest) (. p12 file) export, the password itself, to remember, after the import of the time to use. 3. Install the certificate (. cer) on the machine you want, and import the private key file (. p12). Installs the provisioning profile for the corresponding app. 4. Over, you can use other machines to develop. Note: You must export the private Key cannot generate a copy, only the computer configured with the certificate is available; (the copy is described below Keychain) 2. Provisioning Profile (authorization file) authorization files are authorized for devices such as ipod Touch, IPad, iphone, the device's Udid and app Id are recorded in the file, Even if the authorized device can install or debug the bundle identifier program that corresponds to the app ID recorded in the authorization file. The developer account will choose the app ID when creating the authorization file (add the app ID in the developer account, select a single) and Udid (add up to 100, multi-select in the developer account under devices).
The authorization file is divided into two types, corresponding to the corresponding certificate use: 1) Developer Provisioning profile (Development authorization file) on the computer with the development certificate or copy, The developer chooses the authorization file to install the program to a device in the authorization file record through the computer, and can perform a real-machine test. Note: Make sure that the computer has permissions to debug, that is, the development certificate or copy is installed, the bundle identifier of the program in the development tool and the app ID of the selected authorization file are consistent; The udid of the device that connects the debugs is recorded in the selected authorization file.
2) Distribution Provisioning profile (release authorization file) on the computer that has the certificate issued (that is, the computer with the certificate, only one) makes the beta and release version of the program: The release is published to the app The program file on the store, the developer account choose the Store option when creating the authorization file, choose the app Id, no need to select Udid; Beta is the program file that the tester can sync to the device before it is released, select Adhoc when creating the authorization file for the developer account, select the app ID and Udid, only the selected Udid device may install the program that is made through the authorization file.
3.Keychain (Development key) if the certificate is installed successfully under the certificate will generate Keychain, the above mentioned certificate copy is the computer configured by the certificate to export Keychain (that is. p12 file) installed on other machines, so that the other machine to get the certificate corresponding permissions. Developer certification can make copies keychain distributed to other computers to be installed so that they can be tested on the real machine.
NOTE:distribution certification can only be used by a computer with a configuration certificate (only one) , so even if the export export keychain is installed on another computer, it is not possible for other computers to have certificate permissions.
iOS development-Multiple machine sharing certificate issues