Releases: bitrise-steplib/steps-xcode-archive
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
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
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. (...)