4.3.1

What's Changed

• Allow empty certificate passphrase in #286

Note: we don't recommend using a certificate without a passphrase for security reasons, but it used to work in other Bitrise steps, so we are unifying the behavior across all Xcode steps.

Full Changelog: 4.3.0...4.3.1

4.3.0

Will run xcodebuild -resolvePackageDependencies command to fetch Swift packages, before archiving and exporting. This improves visibility for the time required to fetch packages.
Log elapsed time in the resolve packages dependencies command and later -showBuildSettings commands.

4.2.8

Fixes an issue in the new device registration flow.

4.2.7

What's Changed

Internal fixes and dependency updates

Full Changelog: 4.2.6...4.2.7

4.2.6

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, #276)

4.2.5

Include Xcode >12 specific export options even if an available profile/certificate is not yet available due to the Xcode managed code signing used.

• distributionBundleIdentifier solves the following error: Provide a bundle identifier to select from available reformatters
• manageAppVersionAndBuildNumber (Xcode>13) is also included for consistency

(#275)

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.