Update Fastlane tool version

osx
fastlane

#1

Hi guys
You version of deliver tool is old. This is from fastlane log:

#######################################################################
# deliver 1.13.2 is available. You are on 1.13.1.
# It is recommended to use the latest version.
# Update using 'sudo gem update deliver'.
#######################################################################

There is an error in 1.13.1 which causes a crash when run deliver, you can read more here: https://github.com/fastlane/fastlane/issues/5643

It would be nice if you update the tool!


#2

I’m having different a different deliver issue, mine is failing with:
[18:29:24]: undefined method 'fetch' for nil:NilClass

My local machine is up to date with fastlane, and I was able to use deliver from that machine to upload my app release to iTunes Connect.

The version of deliver on CircleCI, 1.13.1, is 2 versions behind. All of the fastlane tools appear to be slightly behind, and it would be good to update them all soon.


#3

Hey,

We will update every gem we ship out of the box with every OSX image iteration, but Fastlane iterates quicker on their tools than we do on our image at the moment. You can update the Fastlane gem yourself out of circle.yml file though in order to get around this for now, simply add this:

dependecies:
  pre:
    - gem update fastlane

The deliver gem should get updated by running that command as well.

Best,
Costantin


#4

Hi @anon47539524 ;

My iOS builds are timing out due to gem update fast lane requiring a “y” input to overwrite what is installed. (after running a gem update fastlane)

sudo gem update fastlane
Updating installed gems
Updating fastlane
commander-fastlane’s executable “commander” conflicts with commander
Overwrite the executable? [yN]

Do you have any suggestions on getting around this other than disabling the fastlane update?


#5

Hey Julian,

I would suggest this:

yes | sudo gem update fastlane

This should update fastlane just fine on your containers.

Best,
Constantin


#6

Thank you @anon47539524 for the prompt response. That worked.


#7