Releases: bitrise-steplib/steps-xcode-archive
4.7.1
4.7.0
What's Changed
- Add example of code signing setting by @bitrise-silver in #307
- Error message improvements by @godrei in
New Contributors
- @bitrise-silver made their first contribution in #307
Full Changelog: 4.6.0...4.7.0
4.6.0
Notable changes
Authentication parameters used for code signing setup can be overridden using new step inputs (instead of using the globally configured connection for the whole app). Check out the description of the new inputs (api_key_path
, api_key_id
, api_key_issuer_id
) for more details.
What's Changed
- Added conditional for dSYM check on Xcode14. by @matrangam in #301
- Remove Xcode check by @ofalvai in #305
- Override API connection via step inputs by @ofalvai in #303
Full Changelog: 4.5.2...4.6.0
4.5.2
What's Changed
- Update step.yml
- Update go-xcode dependency to pull proper xcconfig file path handling
Full Changelog: 4.5.1...4.5.2
4.5.1
What's Changed
- high-level logs for building a project by @shams-ahmed in #296
Full Changelog: 4.5.0...4.5.1
4.5.0
The "Build settings (xcconfig)" (xcconfig_content
) input can now be a path to a existing .xcconfig
file. Previously it could have been only the contents.
If is empty, no setting is changed. This is required when the -xcconfig
additional option is used.
When xcconfig_content
is set it can be either:
-
Existing
.xcconfig
file path.
Example:./ios-sample/ios-sample/Configurations/Dev.xcconfig
-
The contents of a newly created temporary
.xcconfig
file. (This is the default.)
Build settings must be separated by newline character (\n
).
Example:COMPILER_INDEX_STORE_ENABLE = NO ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES
4.4.0
4.3.3
4.3.2
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