The Step creates an archive using the xcodebuild archive command for your macOS project so you can share it, upload it, or deploy it.
Before you start:
Make sure your certificates are uploaded to Bitrise's Code Signing tab.
To configure the Step:
Under app/pkg export configs:
Under xcodebuild configs:
yes, if you want to run a clean xcodebuild before the archive action. Select no to skip this.yes.Under force archive codesign settings:
xcodebuild to use specified code sign identities or provisioning profiles, you can do so in the inputs under the force archive codesign settings tab.Under step output configs:
xcodebuild command log format in the Output tool input. Available options are xcpretty: The xcodebuild command's output will be prettified by xcpretty, and xcodebuild: Only the last 20 lines of raw xcodebuild output will be visible in the build log. The raw xcodebuild log is exported in both cases..app or .pkg files and the .dSYM.zip files in the Output directory input.yes. This will compress the generated files into a zip file and move them to a folder output_dir.yes.yes to produce more informative logs.If you receive an error about missing signing certificates during this Step, make sure that your certificates are uploaded to Bitrise's Code Signing tab.