Xcode Archive & Export for iOS v4.0.0

Changelog
1

This major release simplifies step inputs and makes them consistent across other Xcode-related steps.

Breaking changes and migration guide

  • If the product_name input is not defined, the name used for build artifacts (IPA, dSYMs, xcarchive) is now based on the PRODUCT_NAME Xcode build settings. Specify a new value as product_name if you want to rename the artifacts.
  • Removed auto-detect option of the distribution_method input. This option has been marked as deprecated for a while. The new default value is development, make sure you select the desired distribution method.
  • New input: xcconfig_contents. Use this input to define arbitrary build config values.
  • Removed input force_team_id in favor of xcconfig_contents. Use DEVELOPMENT_TEAM = value as xcconfig_contents for the same behavior.
  • Removed input force_provisioning_profile in favor of xcconfig_contents. Use PROVISIONING_PROFILE = value as xcconfig_contents for the same behavior. Note: PROVISIONING_PROFILE is deprecated since Xcode 13, make sure to migrate to PROVISIONING_PROFILE_SPECIFIER!
  • Removed input force_code_sign_identity in favor of xcconfig_contents. Use CODE_SIGN_IDENTITY = value as xcconfig_contents for the same behavior.
  • Removed input force_provisioning_profile_specifier in favor of xcconfig_contents. Use PROVISIONING_PROFILE_SPECIFIER = value as xcconfig_contents for the same behavior.
  • Removed workdir input as it was unused.
  • Removed disable_index_while_building input. The default value of xcconfig_contents disables indexing just like before.

Renamed some inputs for consistency across Xcode steps (without any behavior change):

  • export_method → distribution_method
  • team_id → export_development_team
  • is_clean_build → perform_clean_action
  • custom_export_options_plist_content → export_options_plist_content
  • output_tool → log_formatter
3

Hi,

I don’t see xcconfig_contents in Workflow editor. What is the label of this input ?

4

Hi there @alexis.thaveau.s2e :wave:

This input is not directly available in the workflow editor, but can be accessed and modified in the yml file itself. You can see where it is based on the step’s Github repository: steps-xcode-archive/step.yml at master · bitrise-steplib/steps-xcode-archive · GitHub :slight_smile:

5

Hi,
i
xcconfig_content is available in worflow editor, in “xcodebuild configuration” panel, and field “build settings (xcconfig)”

6

This topic was automatically closed after 90 days. New replies are no longer allowed.