2.2.8

Fixes an issue in the new device registration flow.

2.2.7

What's Changed

Internal fixes and dependency updates

Full Changelog: 2.2.6...2.2.7

2.2.6

This Step has been deprecated in favour of the new automatic code signing options on Bitrise.

You can read more about these changes in our blog post: https://blog.bitrise.io/post/simplifying-automatic-code-signing-on-bitrise.

Option A)

The latest versions of the Xcode Archive & Export for iOS, Xcode Build for testing for iOS, and the Export iOS and tvOS Xcode archive Steps have built-in automatic code signing.
We recommend removing this Step from your Workflow and using the automatic code signing feature in the Steps mentioned above.

Option B)

If you are not using any of the mentioned Xcode Steps, then you can replace this iOS Auto Provision Step with the Manage iOS Code signing Step.

2.2.5

Fixed a regression introduced in 2.2.2: an invalid device UUID will not 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

(#98)

2.2.4

Introducing a more robust timestamp parsing fix for #92

2.2.3

Fix step failure caused by a change in the timestamp format provided by App Store Connect API.

Resolves #92

2.2.2

[#90] Remove project team ID detection. This speeds up the step, especially for projects with many targets. Use the apple_id_team_id 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)

2.2.1

(#84) Fixes the issue that sign_uitest_targets Step input is disregarded by the Step.

2.2.0

(#74, #81) Move automatic code signing logic into a shared library and improve App Clip target auto code signing related error handling.

2.1.3

(#79, #80) Fixes the issue that makes the Step failing if the project contains an App Clip target, by ignoring ParentApplicationIdentifiers project capability during Application Identifier capability check.

🥇 Thank you @bwhiteley for the contribution!