Fastlane "undefined method `downcase' for nil:NilClass" error during "Deploy to iTunes Connect" step

Bitrise Build Issue Report template

Description of the issue

During the ‘deploy-to-itunesconnect-deliver’ step, our Xamarin iOS build is hitting this error:
/usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.105.0/fastlane_core/lib/fastlane_core/fastlane_folder.rb:24:in `swift?’: [!] undefined method ‘downcase’ for nil:NilClass (NoMethodError).

I did notice a similar issue here ([!] undefined method `downcase' for nil:NilClass (NoMethodError) on 2.105.0 · Issue #13403 · fastlane/fastlane · GitHub) that suggests the error repros with 2.105.0 of fastlane, but not in 2.014.0.


| (12) deploy-to-itunesconnect-deliver |
| id: deploy-to-itunesconnect-deliver |
| version: 2.14.1 |
| collection: GitHub - bitrise-io/bitrise-steplib: New Bitrise StepLib |
| toolkit: go |
| time: 2018-09-20T16:09:49-07:00 |
| |
INFO[16:09:49] * [OK] Step dependency (go) installed, available.

  • IpaPath: /Users/vagrant/deploy/ActivityApp.iOS.ipa
  • PkgPath:
  • ItunesconUser: [REDACTED]
  • AppPassword:
  • BundleID: [REDACTED]
  • SubmitForReview: yes
  • SkipMetadata: no
  • SkipScreenshots: no
  • SkipAppVersionUpdate: no
  • TeamID: [REDACTED]
  • TeamName:
  • Platform: ios
  • Options:
  • GemfilePath: ./Gemfile
  • FastlaneVersion: latest
  • ITMSParameters: -t DAV
    fastlane version defined: latest, installing…
    $ fastlane “-v”
    fastlane installation at path:

fastlane 2.105.0
Setup took 8.490155 seconds to complete

AppID parameter specified, BundleID will be ignored
$ fastlane “deliver” “–username” “[REDACTED]” “–app” “1279352275” “–team_id” “[REDACTED]” “–ipa” “/var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/ipaOrPkg644818726/tmp.ipa” “–force” “–submit_for_review” “–platform” “ios”
[16:10:04]: Get started using a Gemfile for fastlane Setup - fastlane docs

/usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.105.0/fastlane_core/lib/fastlane_core/fastlane_folder.rb:24:in swift?': [!] undefined method downcase’ for nil:NilClass (NoMethodError)
from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.105.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:71:in run!' from /usr/local/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!’
from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.105.0/deliver/lib/deliver/commands_generator.rb:182:in run' from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.105.0/deliver/lib/deliver/commands_generator.rb:17:in start’
from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.105.0/fastlane/lib/fastlane/cli_tools_distributor.rb:100:in take_off' from /usr/local/lib/ruby/gems/2.5.0/gems/fastlane-2.105.0/bin/fastlane:20:in <top (required)>’
from /usr/local/bin/fastlane:23:in load' from /usr/local/bin/fastlane:23:in
Deploy failed, error: exit status 1

Environment: Hybrid (Xamarin, Ionic, …) on macOS, includes Visual Studio for Mac, Stable channel
Step: Deploy to iTunes Connect (v214.1)


  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : Every time.
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : First hit the issue today (2018.09.20). The most recent previous time we ran this build configuration was on 2018.08.02 (it was successful then).

Local reproduction

_Can it be reproduced on your own Mac/PC? No, it repro’s only as part of the “Deploy to iTunes Connect” workflow step, after the app build has completed successfully.

Build log

Update: I was able to get past the ‘undefined method’ error and successfully complete the build by reverting the ‘deploy-to-itunesconnect-deliver’ step back to version 2.14.0 (from 2.14.1).

1 Like

Hi @tracegmail thanks for letting us know!

Unfortunately there seems to be a Delivery issue with the latest Fastlane version, so for some of these errors downgrading is a suitable workaround.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.