You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow passing a file path to an existing xcconfig file, instead of providing the file contents directly.
* `xcconfig_content` can now be a path to a xcconfig file, or left empty. This allows using a custom xcconfig file that already exists in the repository.
Copy file name to clipboardExpand all lines: README.md
+35-2Lines changed: 35 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ To configure the Step:
29
29
30
30
Under **xcodebuild configuration**:
31
31
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.
32
-
2.**Build settings (xconfig)**: Build settings to override the project's build settings. The build settings must be separated by a newline character (`\n`).
32
+
2.**Build settings (xcconfig)**: Build settings to override the project's build settings. Can be the contents, file path or empty.
33
33
3.**Perform clean action**: If this input is set, a `clean` xcodebuild action will be performed besides the `archive` action.
34
34
35
35
Under **Xcode build log formatting**:
@@ -67,6 +67,38 @@ Add this step directly to your workflow in the [Bitrise Workflow Editor](https:/
67
67
68
68
You can also run this step directly with [Bitrise CLI](https://github.com/bitrise-io/bitrise).
69
69
70
+
### Examples
71
+
72
+
Build a development IPA:
73
+
```yaml
74
+
- xcode-archive:
75
+
inputs:
76
+
- project_path: ./ios-sample/ios-sample.xcodeproj
77
+
- scheme: ios-sample
78
+
- distribution_method: development
79
+
```
80
+
81
+
Build a development IPA with custom xcconfig content:
82
+
```yaml
83
+
- xcode-archive:
84
+
inputs:
85
+
- project_path: ./ios-sample/ios-sample.xcodeproj
86
+
- scheme: ios-sample
87
+
- distribution_method: development
88
+
- xcconfig_content: |
89
+
CODE_SIGN_IDENTITY = Apple Development
90
+
```
91
+
92
+
Build a development IPA with custom xcconfig file path:
@@ -78,7 +110,7 @@ You can also run this step directly with [Bitrise CLI](https://github.com/bitris
78
110
| `scheme` | Xcode Scheme name. The input value sets xcodebuild's `-scheme` option. | required | `$BITRISE_SCHEME` |
79
111
| `distribution_method` | Describes how Xcode should export the archive. | required | `development` |
80
112
| `configuration` | Xcode Build Configuration. If not specified, the default Build Configuration will be used. The input value sets xcodebuild's `-configuration` option. | | |
81
-
|`xcconfig_content`| Build settings to override the project's build settings. Build settings must be separated by newline character (`\n`). Example: ``` COMPILER_INDEX_STORE_ENABLE = NO ONLY_ACTIVE_ARCH[config=Debug][sdk=*][arch=*] = YES ``` The input value sets xcodebuild's `-xcconfig` option.||`COMPILER_INDEX_STORE_ENABLE = NO`|
113
+
| `xcconfig_content` | Build settings to override the project's build settings, using xcodebuild's `-xcconfig` option. If empty, no setting is changed. This is required when the `-xcconfig` additional option is used. When set it can be either: 1. Existing `.xcconfig` file path. Example: `./ios-sample/ios-sample/Configurations/Dev.xcconfig` 2. 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 ``` | | `COMPILER_INDEX_STORE_ENABLE = NO` |
82
114
| `perform_clean_action` | If this input is set, `clean` xcodebuild action will be performed besides the `archive` action. | required | `no` |
83
115
| `xcodebuild_options` | Additional options to be added to the executed xcodebuild command. | | |
84
116
| `log_formatter` | Defines how `xcodebuild` command's log is formatted. Available options: - `xcpretty`: 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 will be exported in both cases. | required | `xcpretty` |
@@ -89,6 +121,7 @@ You can also run this step directly with [Bitrise CLI](https://github.com/bitris
89
121
| `passphrase_list` | Passphrases for the provided code signing certificates. Specify as many passphrases as many Code signing certificate URL provided, separated by a pipe (`\|`) character. Certificates without a passphrase: for using a single certificate, leave this step input empty. For multiple certificates, use the separator as if there was a passphrase (examples: `pass\|`, `\|pass\|`, `\|`) | sensitive | `$BITRISE_CERTIFICATE_PASSPHRASE` |
90
122
| `keychain_path` | Path to the Keychain where the code signing certificates will be installed. | required | `$HOME/Library/Keychains/login.keychain` |
91
123
| `keychain_password` | Password for the provided Keychain. | required, sensitive | `$BITRISE_KEYCHAIN_PASSWORD` |
124
+
| `fallback_provisioning_profile_url_list` | If set, provided provisioning profiles will be used on Automatic code signing error. URL of the provisioning profile to download. Multiple URLs can be specified, separated by a newline or pipe (`\|`) character. You can specify a local path as well, using the `file://` scheme. For example: `file://./BuildAnything.mobileprovision`. Can also provide a local directory that contains files with `.mobileprovision` extension. For example: `./profilesDirectory/` | sensitive | |
92
125
| `export_development_team` | The Developer Portal team to use for this export Defaults to the team used to build the archive. Defining this is also required when Automatic Code Signing is set to `apple-id` and the connected account belongs to multiple teams. | | |
93
126
| `compile_bitcode` | For __non-App Store__ exports, should Xcode re-compile the app from bitcode? | required | `yes` |
94
127
| `upload_bitcode` | For __App Store__ exports, should the package include bitcode? | required | `yes` |
returnConfig{}, fmt.Errorf("`-xcconfig` option found in XcodebuildOptions (`xcodebuild_options`), please clear Build settings (xcconfig) (`xcconfig_content`) input as only one can be set")
0 commit comments