4.2.6

Fixes an issue in the new device registration flow.

4.2.5

What's Changed

Internal fixes and dependency updates

Full Changelog: 4.2.4...4.2.5

4.2.4

Fixed an issue affecting workflows with multiple automatic code signing Steps. A missing check could result in selecting an unavailable certificate:

❌  error: No certificate for team 'AAABBBCCC' matching 'dcdcdc' found: Select a different signing certificate for CODE_SIGN_IDENTITY, a team that matches your selected certificate, or switch to automatic provisioning. (...)

(bitrise-io/go-xcode#150, #38)

4.2.3

When using Automatic code signing with the register_test_devices option set to yes, an invalid device UUID will no longer cause the Step to fail.

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

(#37)

4.2.2

Introducing a more robust timestamp parsing fix for Appstoreconnect responses.

4.2.1

[#35] 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.0

Changes

Adding support for Xcode manage version and build number (App Store Connect). This will change the version and build numbers of all content in your app only if the is an invalid number (like one that was used previously or precedes your current build number). The input will not work if export options plist content input has been set. Default set to No.

4.1.0

Added support for automatically managing code signing assets

Will choose automatically between xcodebuild-managed and Bitrise-managed automatic 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.

(#26 , #27 , #28 , #29 , #30 , #31 , #32)

4.0.0

[#23] Clean up and standardize step inputs, update descriptions

Breaking changes to step inputs

• export method has been renamed to distribution_method to align with other Xcode steps
• Removed previously deprecated auto-detect option of distribution_method. Please select the desired method explicitly (development, app-store, ad-hoc, enterprise)
• custom_export_options_plist_content input has been renamed to export_options_plist_content to align with other Xcode steps
• team_id input has been renamed to export_development_team
• verbose_log input now defaults to false

3.0.0

Remove legacy export (available before Xcode 9) support.