If you wish to use the automatic code signing options of Bitrise Steps, there are a few limitations to keep in mind.
The limitations only apply if all three of the following conditions are true:
In your Xcode project, you do NOT use the Automatically manage signing option.
On Bitrise, you use Apple ID or Step inputs for authentication when connecting to Apple services. If you use API key authentication, these limitations don't apply.
You run your builds on Xcode 12 or earlier versions. With Xcode version 13 and above, the limitations don't apply.
Let's go through the limitations!
Can't configure certain App ID capabilities
You can add new capabilities to an Xcode project during a Bitrise build, even without running it locally at first. However, certain capabilities can't be added this way:
App Groups: can’t enable missing App Groups.
Apple Pay Payment Processing: can’t enable missing Merchant IDs.
iCloud: can’t enable missing iCloud Containers.
Push Notifications: can’t set Development SSL Certificate and Production SSL Certificate.
Sign In with Apple: enable as a primary App ID/Group with an existing primary App ID and Server to Server Notification Endpoint.
Mac Catalyst: can’t Choose a bundle ID configuration for your existing Mac app.
Can't register a new App Clip App ID
If the limitations apply to your project, Bitrise can't register a new ID for an App Clip. If you have an App Clipp target in your Xcode project, you should first build the project locally so that Xcode can create an identifier for it.