Managing iOS code signing files - manual provisioning

To manage your code signing files manually, you need to upload your .p12 signing certificates and the app's provisioning profiles.

You always need to upload at least a Developer certificate and a Development type provisioning profile! That is necessary for our Xcode Steps to be able to test and build your apps properly.

Generating code signing files

If you don't have the necessary code signing files ready, you can generate new files: Generating iOS code signing files

To upload the code signing files to Bitrise, first you need to export the files in the .p12 file format: you can do this manually or using Bitrise's open source codesigndoc tool. Once you successfully exported the files, you need to upload them to Bitrise. You have three options:

To manually upload your code signing files to Bitrise:

  1. Make sure you have your .p12 certificates and provisioning profiles exported and ready. You can export the files using either of two options:

  2. Open your app on Bitrise.

  3. Go to the Workflow tab.

  4. Go to the Code Signing tab.

  5. Add the certificates and provisioning profiles in the Add Provisioning Profile(s) and the Add the private key (.p12) for signing fields, respectively.

    Uploading certificates and Provisioning Profiles

    For a MacOS app, the provisioning profile file extension is .provisionprofile; for an iOS app, the file extension is .mobileprovision.

  6. Make sure you have the Certificate and profile installer Step in your app’s Workflow. You can check it on the Workflow tab of the Workflow Editor.

    Please note that these Steps must be BEFORE the Steps that archive and export your app (for example, Xcode Archive & Export for iOS) in your Workflow.