iOS code signing - troubleshooting

To make iOS code signing work on Bitrise, you generally need to get three things right:

A provisioning profile.
A .p12 certificate file.
Setting the Select method for export input of the Xcode Archive & Export for iOS Step.

To get your code signing files, you can:

If you suspect an error is related to code signing, there is almost certainly a problem with one of these three. When trying to build an iOS app on Bitrise, we strongly recommend generating an .ipa file of the app locally, on your own machine first. If that fails, the build will certainly fail on Bitrise, too.

Let’s look into what you can do to make sure code signing works!

The Xcode Archive & Export for iOS Step fails ⚓

If the Step fails, check the logs. If you see the message: Code signing error then this guide can hopefully help you find the solution!

Most of the time, this error means your project is missing either the correct .p12 certificate file or the correct provisioning profile - or the Select method for export input of the Step is set incorrectly.

Manual provisioning ⚓

If you manually upload your provisioning profiles and use the Certificate and profile installer Step to install your code signing files, read on.

If you use the iOS Auto Provision with App Store Connect API Step, skip to Automatic provisioning.

Check that you have both a .p12 certificate and a provisioning profile uploaded to Bitrise.

To do so, go to your app’s Workflow Editor and check the Code Signing tab.
Check that the provisioning profile and the .p12 certificate of your project match.

A Development type provisioning profile requires a Development certificate. An App Store, Ad-hoc or Enterprise type provisioning profile requires a Distribution certificate. You can check the compatibility on the Code Signing tab: click Show matching Certificates, Devices & Capabilities under any provisioning profile.
Check that the uploaded code signing files belong to the correct team IDs.

Also, make sure the provisioning profile is for the correct Bundle ID.
Check that your uploaded code signing files are valid!

Remember that these files can and do expire or get revoked.
Check the Select method for export input of the Step in the Workflow Editor.

If, for example, it is set to ad-hoc or app-store, you need a Distribution type .p12 certificate file and either an Ad-hoc or an App Store type provisioning profile.
Check if the capability lists in the iOS app and in the provisioning profile uploaded to the Developer Portal match.

Xcode managed signing

If you use Xcode managed signing, the Step only accepts an Xcode managed provisioning profile.

Read more about it in Apple’s Technical Q&A.

Automatic provisioning ⚓

With the iOS Auto Provision with App Store Connect API Step, you do not need to manually upload a provisioning profile to Bitrise. You only need a certificate.

Check that you have a .p12 certificate uploaded to Bitrise.

To do so, go to your app’s Workflow Editor and check the Code Signing tab.

Check that the uploaded code signing files belong to the correct team IDs.

Also, make sure the provisioning profile is for the correct Bundle ID.
Check that your uploaded certificate is valid!

Remember that these files can and do expire or get revoked.
Check the Select method for export input of the Step in the Workflow Editor.

If, for example, it is set to ad-hoc or app-store, you need a Distribution type .p12 certificate file.
Check if the certificate is locked. If it is, check if the password is correct!

When you use the iOS Auto Provision with App Store Connect API Step, using Xcode managed signing is an important factor. Let’s go through what can happen depending on whether you use the option.

If Xcode managed signing is enabled in the iOS app ⚓

Check the value of the Should the step try to generate Provisioning Profiles even if Xcode managed signing is enabled in the Xcode project? input in the iOS Auto Provision with App Store Connect API Step.
- If it’s set to no, the Step will look for an Xcode Managed Provisioning Profile on the Apple Developer Portal.
- If it’s set to yes, the Step will generate a new manual provisioning profile on the Apple Developer portal for the project.
Check if the capability lists in the iOS app and in the provisioning profile on the Developer Portal match.

This is only relevant if the iOS Auto Provision with App Store Connect API Step is set to NOT generate a profile.

If Xcode managed signing is disabled in the iOS app ⚓

If you uncheck Xcode managed signing, the iOS Auto Provision with App Store Connect API Step generates a new provisioning profile on the Apple Developer portal for the project when running a build. This profile will be up to date with all of the capabilities and developer devices.

Have you exceeded the file count limit of the provisioning profiles? ⚓

The maximum number of provisioning profiles and .p12 certificates you can upload to the Code Signing tab is 30. If you’ve already reached this limit and wish to use even more, then here are a few tips on how to use even more provisioning profiles:

Use the iOS Auto Provision with App Store Connect API Step. This only requires the code signing identities (certificates with .p12 extension) to be uploaded to Bitrise. You can download the provisioning profiles from the Apple Developer portal on-the-fly during the build if you have connected your Apple Developer account to Bitrise.
You can create a .zip file containing the required certificates/profiles. In this case, you don’t need to upload any certificates/profiles on Bitrise. During the build you can download the .zip file and update the certificate/profile related inputs of the Certificate and Profile Installer Step to match the path to the certificate/profile on the build machine. Note that the Certificate and Profile Installer Step supports local paths and URLs for certificates and profiles.
You can host the profiles and certificates yourself, and only add an URL that is pointing to a given certificate/profile to the workflow.

Also note that multiple URLs can be specified for both the certificate and profile inputs. Make sure you separate them with a pipe (|) character.

The iOS Auto Provision with App Store Connect API Step fails ⚓

The iOS Auto Provision with App Store Connect API Step manages your provisioning profiles for you: it downloads the profiles from the Apple Developer portal and installs them for you. Here’s what you can do if this Step fails:

If you are trying to use it with a Xamarin app, you will have to swap it for the Certificate and profile installer Step. Automatic provisioning is not supported for Xamarin apps.
Before trying to use this Step, generate an .ipa file locally - with the same export method you want to use on Bitrise - to ensure that the profiles are uploaded to the Apple Developer portal.
Make sure that your Bitrise account is connected to the Apple Developer portal and that you have at least an Admin role in your Apple Developer team.

Test device already registered ⚓

If the iOS Auto Provision with App Store Connect API Step fails with this error message, it is likely that you registered a specific test device on Bitrise twice.

Check out if the same UDID has been registered twice:

Open the app on Bitrise.
Go to the Team tab.
Scroll down and click the Download list of test devices button.

The result will be in json format: check if the same UDID appears twice. If so, it has to be removed from the account to which it was registered.

Open the top-right menu and click Account settings.
On the left, click Test devices.
Remove one of the duplicated devices.

Could not install the app on a device ⚓

To install iOS apps on a given device, you have to either:

Export an .ipa file with the development export method, with the device’s UDID registered in the provisioning profile used for the export.
Export an .ipa file with the ad-hoc export method and install the app via the public install page generated by the Deploy to Bitrise.io Step.

Check that the device UDID is included in the app’s provisioning profile.
- If you use manual provisioning, check the provisioning profile you uploaded to Bitrise.
- If you use automatic provisioning, Should the step try to generate Provisioning Profiles even if Xcode managed signing is enabled in the Xcode project? input is set to no in the iOS Auto Provision with App Store Connect API step: check the provisioning profile on the Apple Developer Portal.
- If you use automatic provisioning, and the Should the step try to generate Provisioning Profiles even if Xcode managed signing is enabled in the Xcode project? input is set to yes in the iOS Auto Provision with App Store Connect API Step: check that the device is registered to the developer team on the Apple Developer portal.
Check the logs to see if the Xcode Archive & Export for iOS Step used the provisioning profile with the device’s UDID in it.

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.

You can easily create a signed IPA for your Xamarin app with Bitrise. All you need to do is set the relevant inputs of our Xamarin Archive Step!