Collecting code signing files ⚓
If you collected all the necessary files with the
codesigndoc tool, proceed to uploading them and setting up your Workflow. You can upload the files manually or you can do this with the
codesigndoc tool, too!
Uploading code signing files ⚓
- Open your app on your Dashboard.
- Select the Workflow Editor tab.
- Select the Code Signing tab.
Make sure that the provisioning profiles and the .p12 files are uploaded.
If not, add them in the Add Provisioning Profile(s) and the Add the private key (.p12) for signing fields, respectively.
For a MacOS app, the provisioning profile file extension is
.provisionprofile; for an iOS app, the file extension is
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.
codesigndoc does not pick up one or more distribution .p12 files and/or provisioning profile(s), you can export those manually (the .p12 file from the Keychain Access app, provisioning profiles from Apple Developer Portal), just like you would when you transfer these files between Macs.
But even if
codesigndoc does not find all the files, you should upload all the files collected by
codesigndoc**! The base files collected by
codesigndoc are essential for your app’s code signing: without those it’s not possible to create a signed .ipa of the app!
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...