Releases: bitrise-steplib/steps-xcode-build-for-test
Releases · bitrise-steplib/steps-xcode-build-for-test
1.4.0
What's Changed
- Add a new feature to the
Build settings (xcconfig)
Step Input: allow passing a file path to an existing xcconfig file, instead of providing the file contents directly.
Full Changelog: 1.3.2...1.4.0
1.3.2
What's Changed
- Added equals comparison for result file mod time. by @matrangam in #34
- Fix Apple ID time format handling by @ofalvai in #36
- Reverted to more concise time check; added logs to better surface failure reasons. by @matrangam in #35
New Contributors
- @matrangam made their first contribution in #34
Full Changelog: 1.3.1...1.3.2
1.3.1
What's Changed
- Allow empty certificate passphrase in #32
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: 1.3.0...1.3.1
1.3.0
1.2.5
1.2.4
1.2.3
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. (...)
1.2.2
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
(#27)