Manage your code signing files on bitrise.io. You can use iOS automatic provisioning to automatically download or generate the required Provisioning Profiles for your project.
With automatic provisioning, the
iOS Auto Provision step will manage the Provisioning Profiles. You only have to upload the .p12 certificate files manually to bitrise.io.
Before setting up automatic provisioning in your workflow, make sure that:
- you collected the required files with codesigndoc. You can also upload the distribution and development certificates with the tool!
- you have at least Admin role in the developer portal team.
- your Apple Developer account is connected to bitrise.io.
- Apple Developer Portal integration to your Bitrise project is enabled.
Once you are ready, proceed to uploading your files and setting up your workflow:
- Open your app on your
- Select the
- Select the
Make sure you have the .p12 certificate files uploaded. If not, add the .p12 files in the
Add the private key (.p12) for signingfield.
For a MacOS project, the Provisioning Profile file extension is
.provisionprofile; for an iOS project, the file extension is
- Make sure that you do NOT have the
Certificate and profile installerstep in your Workflow. If you have both
iOS Auto Provisionand
Certificate and profile installersteps in your Workflow, your build will fail.
iOS Auto Provisionstep to your app’s Workflow. You can check it on the
Workflowtab of the
Please note that this step must come AFTER any dependency installer step in your workflow, such as
Run CocoaPods installor
Carthage. Make sure that you do NOT modify your Xcode project between the
iOS Auto Provisionand the
Xcode Archive & Export for iOSsteps. For example, do not change the bundle ID after the
iOS Auto Provisionstep.
- Fill the required inputs of the step.
The Developer Portal team id- find this on the Membership Details page of your Apple Developer Portal account
Distribution type- make sure its value matches the value of the
Select method for exportinput in the
Xcode Archive & Export for iOS step.
Scheme- you can restrict which targets to process.
Optionally, you can set one more input if you use the Automatically manage signing option in Xcode: if the input marked with
Should the step try to generate Provisioning Profiles even if Xcode managed signing is enabled in the Xcode project? is set to
true then the step will try to generate a profile. If you use manual code signing in Xcode, this input has no effect.
codesigndoc does not pick up one or more distribution .p12 files, you can export those manually from the
Keychain Access app, just like you would when you transfer these files between Macs.
You can upload, update, list, and delete iOS code signing files with the relevant Bitrise API. In this guide we show you how and in what order to use those...
You can manually specify the code signing configuration in your Gradle configuration so that your app gets signed during the build process.
You can create a signed APK using the Android Sign Step in your Bitrise workflow. This Step is configured to run if you have already uploaded your keystore file to...