1.9.0

• NEW INPUT: export_all_dsyms
  If this input is set to yes step will collect every dsym (.app dsym and framwork dsyms) in a directory, zip it and export the zipped directory path. Otherwise only .app dsym will be zipped and the zip path exported.

1.8.5

• [c4f9425] release prep - v1.8.5
• [1742332] step.yml revision

1.8.4

• [70fde9c] bitrise.yml revision & v1.8.4
• [c4ab5f9] Merge pull request #45 from bitrise-io/feature/debug-print-paths
• [e85a01c] debug print the exposed paths

1.8.3

• step ensures if xcarchive generated after archive command

1.8.2

• more env unset - for no applicable device found fix, see: http://stackoverflow.com/questions/33041109/xcodebuild-no-applicable-devices-found-when-exporting-archive

1.8.1

• allow to use deprecated export method: use_deprecated_export
• more info about the format of the Code Sign Identity

1.8.0

• DEPRECATION : is_force_code_sign input removed, because of the latest version (1.5.0 ) of step certifcate and profile installer no more exports BITRISE_PROVISIONING_PROFILE_ID and BITRISE_CODE_SIGN_IDENTITY. This envs were used if xcode archive step's is_force_code_sign was true.
  From now you can direct specify force_code_sign_identity and force_provisioning_profile as input of xcode archive step.

1.7.3

$GEM_HOME fix/workaround:

Fixes the Error Domain=IDEDistributionErrorDomain Code=14 "No applicable devices found." error. If $GEM_HOME is set and the project's directory includes a Gemfile, xcodebuild -exportArchive can fail with this error.

To fix this the Step unsets GEM_HOME right before xcodebuild -exportArchive, as that's not required for xcodebuild anyway.

1.7.2

• print xcodebuild full version
• export generated .app directory

1.7.1

• typo fix