Skip to main content

iOS code signing with manual provisioning

Abstract

To manage your code signing files manually, you need to upload your .p12 signing certificates and the app's provisioning profiles to Bitrise. There are multiple ways to do this.

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

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. Once you successfully exported the files, you need to upload them to Bitrise. You have two options:

  • Via an API call.

  • Uploading it manually to Bitrise. This guide focuses on this option.

To manually upload your code signing files to Bitrise:

Admin access only

Only users with the role of admin on the app's team can access all functions of the App Settings page of an app.

  1. Make sure you have your .p12 certificates and provisioning profiles exported and ready. Check out Exporting iOS code signing files for more information.

  2. Open your app on Bitrise.

  3. On the main page of the app, click on the App Settings icon: settings.svg.

    app-settings.png

  4. On the left, select Code signing from the menu.

  5. Add your files:

    • To add a certificate, click the Add .p12 file button. In the dialog box, upload the file and, if required, provide the password for the certificate.

    • To add provisioning profiles, click the Add profile(s) button. In the dialog box, upload the file(s).

  6. Make sure you have the Certificate and profile installerStep 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.

    certificate_and_profile_installer.png
In this section:
app's

A Step is a block of script execution that encapsulates a build task on Bitrise: the code to perform that task, the inputs and parameters you can define for the task, and the outputs the task generates.

A Workflow is a collection of Steps, Environment Variables, and other configurations. When Bitrise starts a build, it runs one or more Workflows according to the configuration defined in the bitrise.yml file.

The Bitrise Workflow Editor allows you to edit your Workflows, configure Steps, upload files (including code signing files) and manage your app's triggers and stacks on a graphical user interface. It is available both online and offline.