The Step archives your Xcode project by running thexcodebuild archive command and then exports the archive into an .ipa file with thexcodebuild -exportArchive command.This .ipa file can be shared, installed on test devices, or uploaded to the App Store Connect.With this Step, you can use automatic code signing in aCI environment without having to use Xcode.In short, the Step:

• Logs you into your Apple Developer account based on theApple service connection you provide on Bitrise.
• Downloads any provisioning profiles needed for your project based on theDistribution method.
• Runs your build. It archives your Xcode project by running thexcodebuild archive command and exports the archive into an .ipa file with thexcodebuild -exportArchive command.This .ipa file can be shared and installed on test devices, or uploaded to App Store Connect.

Before you start:

• Make sure you have connected yourApple Service account to Bitrise.Alternatively, you can upload certificates and profiles to Bitrise manually, then use the Certificate and Profile installer step before Xcode Archive
• Make sure certificates are uploaded to Bitrise'sCode Signing tab. The right provisioning profiles are automatically downloaded from Apple as part of the automatic code signing process.

To configure the Step:

1. Project path: Add the path where the Xcode Project or Workspace is located.
2. Scheme: Add the scheme name you wish to archive your project later.
3. Distribution method: Select the method Xcode should sign your project: development, app-store, ad-hoc, or enterprise.

Underxcodebuild configuration:

1. Build configuration: Specify Xcode Build Configuration. The Step uses the provided Build Configuration's Build Settings to understand your project's code signing configuration. If not provided, the Archive action's default Build Configuration will be used.
2. Build settings (xcconfig): Build settings to override the project's build settings. Can be the contents, file path or empty.
3. Perform clean action: If this input is set, aclean xcodebuild action will be performed besides thearchive action.

UnderXcode build log formatting:

1. Log formatter: Defines howxcodebuild command's log is formatted. Available options arexcpretty: The xcodebuild command's output will be prettified by xcpretty.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.

UnderAutomatic code signing:

1. Automatic code signing method: Select the Apple service connection you want to use for code signing. Available options:off if you don't do automatic code signing,api-keyif you use API key authorization, andapple-idif you use Apple ID authorization.
2. Register test devices on the Apple Developer Portal: If this input is set, the Step will register the known test devices on Bitrise from team members with the Apple Developer Portal. Note that setting this toyes may cause devices to be registered against your limited quantity of test devices in the Apple Developer Portal, which can only be removed once annually during your renewal window.
3. The minimum days the Provisioning Profile should be valid: If this input is set to >0, the managed Provisioning Profile will be renewed if it expires within the configured number of days. Otherwise the Step renews the managed Provisioning Profile if it is expired.
4. TheCode signing certificate URL, theCode signing certificate passphrase, theKeychain path, and theKeychain password inputs are automatically populated if certificates are uploaded to Bitrise'sCode Signing tab. If you store your files in a private repo, you can manually edit these fields.

If you want to set the Apple service connection credentials on the step-level (instead of using the one configured in the App Settings), use the Step inputs in theApp Store Connect connection override category. Note that this only works ifAutomatic code signing method is set toapi-key.

UnderIPA export configuration:

1. Developer Portal team: Add the Developer Portal team's name to use for this export. This input defaults to the team used to build the archive.
2. Rebuild from bitcode: For non-App Store exports, should Xcode re-compile the app from bitcode?
3. Include bitcode: For App Store exports, should the package include bitcode?
4. iCloud container environment: If the app is using CloudKit, this input configures thecom.apple.developer.icloud-container-environment entitlement. Available options vary depending on the type of provisioning profile used, but may include:Development andProduction.
5. Export options plist content: Specifies aplist file content that configures archive exporting. If not specified, the Step will auto-generate it.

UnderStep Output Export configuration:

1. Output directory path: This directory will contain the generated artifacts.
2. Export all dSYMs: Export additional dSYM files besides the app dSYM file for Frameworks.
3. Override generated artifact names: This name is used as basename for the generated Xcode archive, app,.ipa and dSYM files. If not specified, the Product Name (PRODUCT_NAME) Build settings value will be used. If Product Name is not specified, the Scheme will be used.

UnderCaching:

1. Enable collecting cache content: Defines what cache content should be automatically collected. Available options arenone: Disable collecting cache content andswift_packages: Collect Swift PM packages added to the Xcode project

Under Debugging:

1. Verbose logging*: You can set this input toyes to produce more informative logs.