fastlane: Adding export_options to gym not working

New Issue Checklist

Existing issue #10685

Issue Description

Because of issue #10685 I manually changed ‘signingStyle’ to ‘automatic’ in the plist and exporting is working correctly then. So to achieve this via fastlane I added this in my gym command:

export_options: {
                signingStyle: "automatic"
        }

But when I run fastlane the signingStyle of generated plist is still ‘manual’. I don’t want this… Did I do anything wrong or is this een issue in fastlane?!

Sorry I don’t past all content of fast file etc because it contains confidential information. Please ask me if you need some specific parts to answer my question.

Environment

Key Value
OS 10.12.6
Ruby 2.2.4
Bundler? false
Git git version 2.8.1
Installation Source ~/.fastlane/bin/bundle/bin/fastlane
Host Mac OS X 10.12.6 (16G29)
Ruby Lib Dir ~/.fastlane/bin/bundle/lib
OpenSSL Version OpenSSL 1.0.2g 1 Mar 2016
Is contained false
Is homebrew true
Is installed via Fabric.app false
Xcode Path /Applications/Xcode.app/Contents/Developer/
Xcode Version 9.0.1

System Locale

Variable Value
LANG en_US.UTF-8
LC_ALL en_US.UTF-8
LANGUAGE en_US.UTF-8

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 2
  • Comments: 40 (10 by maintainers)

Most upvoted comments

Pinning to 2.62.0 in the Gemfile resolves the issue, however, I’ve also found that doing anything with sigh in the fastfile causes the signingStyle to resort to manual. We had calls to sigh repair and sigh in one of our fastfiles and that was causing the signingStyle to switch to “manual”. Removing all calls to sigh seemed to fix the issues.

We’re running into the same issue. We use automatic code signing and after updating to fastlane 2.62.1 builds are failing because PR #10508 appears to force xcodebuild to use manual code signing. Hand editing the plist to set signingStyle to automatic fixes the issue but gym ignores export_options: { signingStyle: "automatic" } and still sets the signingStyle to manual.

Downgrading to fastlane 2.62.0 fixes the issue for me.