Background: The company project occasionally needs to modify the iOS client's code, the IDE is not too familiar.
The developer account is a unified company. Key documents include the. p12 file and the mobileprovision description file.
You need to first add your iphone's Udid to the developer account to the developer account. P12 and. mobileprovision file Double-click P12 file, open Keychain tool automatically, enter P12 password Double-click the. mobileprovision file, it will automatically install to Xcode, there are a lot of description files, each Click to import it in Xcodetarget->build Settings->code signing-> Provisioning profile can choose "Automatic", Xcode will choose the default configuration file and certificate according to the target's "Bundle identifier". You can also manually select a match yourself.
reprint: A fully written blog about how to apply for an account, create an export certificate, and describe a file : http://www.jianshu.com/p/9d9e3699515e The provisioning profile contains all of the above: certificate, App ID, device, suffix named. mobileprovision. A provisioning profile corresponds to a explicit app ID or wildcard app ID.
Provisioning profile determines which certificate (public key)/private key combination (key pair/signing Identity) Xcode is used to sign the application (signing Product). embedded in the. IPA package when the application is packaged. Provisioning Profile Packs All this information together to make it easier for us to use when debugging and publishing packages are packaged. In this way, as long as the different circumstances to choose a different provisioning profile can be. Provisioning profile is also divided into development and distribution two categories, the validity period is the same as certificate. The development version of Provisioningprofile is used for development debugging, and the distribution version of Provisioningprofile is primarily used to submit the App Store audit, which does not specify the devices of the development test. Xcode development, it is necessary to configure the corresponding description file under Xcodetarget->build settings->code signing->provisioning profile (provisioning Profiles), and then in the Code signing identity dropdown You can choose identities from Profile "..." (that is, certificates contained in provisioning profile). In Xcodetarget->build settings->code signing->provisioning profile can choose "Automatic", Xcode according to the Target's "Bundle Identifier "Select the default profile and certificate.