4.2.4

When using Automatic code signing with the register_test_devices Input set to yes, an invalid device UUID will no longer cause the Step to fail. This is a regression introduced in 4.2.1.

Automatic code signing failed: failed to ensure test devices: failed to register Bitrise Test device on Apple Developer Portal: POST https://api.appstoreconnect.apple.com/v1/devices: 409

(#274)

4.2.3

Introducing a more robust timestamp parsing fix for Appstoreconnect responses.

4.2.2

[#271] Remove project team ID detection. This speeds up the step, especially for projects with many targets. Use the export_development_team input to explicitly define the team ID in ambiguous cases (for example, when Apple ID based connection is used and the account belongs to multiple teams)

4.2.1

(#268, #269, #270 ) step.yml and go dependencies update.

4.2.0

#267 Bitrise-managed automatic code signing now considers the local code signing assets. If there is a valid Provisioning Profile for a given target, it won't be downloaded again from the Apple Developer Portal.

4.1.0

Added support for automatically managing code signing

Will choose automatically between xcodebuild-managed and Bitrise-managed signing.
Requirements for using xcodebuild-managed code signing assets:

• The Xcode project has the Automatically manage signing option turned on.
• The The minimum days the Provisioning Profile should be valid (min_profile_validity) Input is left on the default (0) value
• Xcode version in use is at least 13.
• API key is used for authentication, not Apple ID.

If the above conditions are not met, will use Bitrise-managed signing.

xcodebuild for managing code signing assets with API key

Uses the CI integration support introduced in Xcode 13 to manage app IDs and profiles. (https://developer.apple.com/videos/play/wwdc2021/10204/)

Bitrise-managed code signing assets

Integrates the functionality of the iOS Auto Provision with App Store Connect API and iOS Auto Provision with Apple ID Step.

Migration

Preserving the valid certificates to the Bitrise Code Signing tab is still a requirement.

1. First, set the new Automatic code signing (automatic_code_signing) input to api_key or apple_id.
   • Must use Apple services connection (https://devcenter.bitrise.io/en/accounts/connecting-to-services/apple-services-connection.html), setting Apple authentication via Step inputs is not supported as of now.
2. Configure the Register test devices and The minimum days the Provisioning Profile should be valid inputs, if they were set to a custom value previously.
3. Remove iOS Auto Provision and Certificate and profile installer Steps from the workflow. This is possible after all Xcode Steps that require code signing are migrated. Having multiple Steps managing code signing is not an issue.

Step specific migration notes:

• iOS Auto Provision with Apple ID Step
  • For more reliable code signing, move to API key authentication. (Unless using Enterprise distribution method).
• Certificate and profile installer Step
  • This is possible if migrating to automatically managed code signing assets (Manually installing Provisioning Profiles is unsupported)
  • After removal of Certificate and profile installer, only profiles can be removed from the Code signing tab.

(#261, #266)

4.0.4

(#260) Artifact name falls back to Scheme if PRODUCT_NAME Build Setting is empty.

4.0.3

Display verbose debug logs again. (#259)

4.0.2

Disabled Xcode managed version and build number. This option was introduced in Xcode 13, and could result in unexpected change of the version in all plists and frameworks in the IPA.
If you need to manually enable this options, please specify a custom export options plist.

The Xcode provided export options plist key, for reference:

manageAppVersionAndBuildNumber
Should Xcode manage the app's build number when uploading to App Store Connect? Defaults to YES.

(#256)

4.0.1

[#258] Use scheme as a fallback product name when reading it from the build settings fails