To run a build of your iOS app on Bitrise, you will need to provide code signing files in some way. The code signing of iOS projects requires:
- Signing certificates in a .p12 format
- Provisioning Profile file(s) matching your project (team ID, bundle ID, …)
- a script, tool or step which installs these files in the build environment.
You can store your code signing files and create a signed .ipa file for your iOS project (Xcode or Xamarin), or a signed .app or .pkg file for your MacOS project on bitrise.io. You can manually upload all the required files (Provisoning Profiles and .p12 certificate files) or you can use automatic provisioning to automatically generate and manage Provisioning Profiles from a connected Apple Developer account. We’ll show you how to use both options!
We also support using Xcode’s Automatically manage signing option, with both manual and automatic provisioning.
iOS code signing procedure ⚓
The basic workflow of code signing is pretty straightforward:
- Collect the required files with our codesigndoc tool.
- Upload your code signing files to bitrise.io. You can upload the files using
codesigndocor manually on the website. For Provisioning Profiles, you can use:
- Use the
Xcode Archive & Export for iOSor the
Xamarin Archivestep to create a signed
iOS code signing with third party tools ⚓
Even if you use a third party tool to manage your code signing files, and you don’t plan to upload any code signing file to bitrise.io, you should keep the
Certificate and profile installer step in your Workflow. This is because certain tools were not designed to work in an ephemeral environment, or in a full clean macOS install, and the
Certificate and profile installer includes common workarounds for this situation. It’s not guaranteed that it will help with the tool of your choice, but it won’t cause any issue either.