1.4.1

The .xcarchive is not stored in the Deploy dir anymore as it's usually significantly larger than any other generated artifact file and it's rarely useful to have as an artifact; no need to deploy it

1.4.0

• build tool option : use xctool or xcodebuild for the archive (xctool is now the default) | thanks to @gkiki90
• configuration option : in addition to specifying an Xcode Scheme you can now define an Xcode Configuration as well | thanks to @vincentsaluzzo
• log revision

1.3.6

fix for OS X Yosemite and earlier OS X versions

1.3.5

IPA discovery fix, in case the IPA would be generated with a "non standard" name (if you change related Xcode project settings)

1.3.4

Ad Hock distribution detection fix

1.3.3

• Just a little bit less verbose logging 😉

1.3.2

• Fixing an RVM related issue, which caused exportArchive: No applicable devices found : #13

1.3.1

• fix: in case the archive path (Scheme's name) contains whitespace / space character(s)

1.3.0

• Implemented exportOptionsPlist xcodebuild option handling for Xcode 7+ (fixes: #11 & #7)
• added the is_clean_build option

1.2.0

• Force code signing option

- is_force_code_sign: "no"
    opts:
      title: "Use force code signing attributes?"
      description: |-
        If set to "yes" then it'll use the `PROVISIONING_PROFILE` (set
        to the value of the `$BITRISE_PROVISIONING_PROFILE_ID` environment)
        and `CODE_SIGN_IDENTITY` (set to the value
        of the `$BITRISE_CODE_SIGN_IDENTITY` environment)
        Xcode Command Line parameters,
        for force the use of specified Certificate and Provisioning Profile,
        to the ones