During the development of your iOS app you will need multiple types of distributions for different purposes, such as internal testing or deployment to the App Store. The good news is that this does not require setting up two separate workflows on bitrise.io.
Before you start ⚓
Before you start, you need to:
- Upload different types of .p12 certificates (for example, developer and distribution certificates).
- Upload the associated provisioning profiles (or managing them automatically with the iOS Auto Provisioning Step).
If all your code signing files are in place, proceed to setting up your Workflow.
Re-signing an .ipa file ⚓
In this example we’ll be setting up a Workflow to create two signed .ipa files: one with the
development and one with the
app-store export method.
Make sure you have the Xcode Archive & Export for iOS Step in your Workflow.
Please note that this Step must come AFTER either the Certificate and profile installer or the iOS Auto Provisioning Step in your Workflow.
In the list of input variables, navigate to Select method for export and select development from the dropdown menu.
- Add the Export iOS and tvOS Xcode archive Step to your Workflow.
In the list of input variables, navigate to Select method for export and select app-store from the dropdown menu.
And you’re done! Feel free to add multiple Export iOS and tvOS Xcode archive Steps to your Workflows to create multiple different signed .ipa files if necessary.
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...
Manage iOS code signing on Bitrise: collect and upload your code signing files using our tools, and export your app with the export method you specify.
The open source codesigndoc tool runs a clean Xcode/Xamarin Studio Archive on your Mac, and analyzes the generated archive file.