step failing because bundler isn't up to date about steps-ios-auto-provision

[cain004]

I'm also seeing this issue with the Xcode 11.3.x stack. Any ETA?

[cathyharmon]

There is a fix in progress, but there are several work-arounds you can use:

You can use a script step prior to the ios-auto-provision step to install the bundler version:

`gem install bundler:1.17.3'

Or you can delete the BUNDLED WITH lines you specified
Or you can delete the Gemlock.file

Hopefully this will be fixed very soon and these workarounds will not be needed!

[cain004]

A script step prior actually fails:

+------------------------------------------------------------------------------+

| (3) [email protected]                                                             |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.5                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2020-01-14T19:50:57Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
+ gem install bundler:1.17.3
ERROR:  Error installing bundler:
	"bundle" from bundler conflicts with /Users/vagrant/.rbenv/versions/2.6.5/bin/bundle

Is there a bitrise environment var with the path to where this is so I can delete the Gemlock.file?

[cain004]

I think you meant
gem install bundler --force -v 1.17.3
This is working for me now. Thanks!
For those interested, add a Script step just before the iOS Auto Provision. Below is the simple script I used:

#!/usr/bin/env bash
# fail if any commands fails
set -e
# debug log
set -x

# write your script here
gem install bundler --force -v 1.17.3

[cathyharmon]

Hello,

There have been very recent releases that have become available. These should be reflected soon in the rebuild of the Xcode Edge stack so hopefully this won't be a problem on Monday.

In the meantime, you can uninstall/install the version you need in a script step. Also, you might want to check out the following community step:

https://github.com/FutureWorkshops/bitrise-step-install-bundler

[arielelkin]

Hi @cathyharmon

Happy Monday! We're still seeing the same issue. Do you have an ETA for when this will be resolved?

Thanks

[cathyharmon]

My apologies! I misread the issue and thought you were asking for the latest version of the bundler to be provided in the Xcode stack instead of bundler 2.1.2.

Looking at the error, it seems that bundler 1.17.3 is being looked for and not found. Not surprising as the stack provides bundler 2.1.2!

This appears to be a problem with RubyGems and dealing with the version of bundler used. (see rubygems/bundler#6882)

Can you check your Gemfile.lock file and delete the BUNDLED WITH section? Others have deleted their `Gemfile.lock' file and recreated under the newer version of the bundler.

[pabdavis]

Hi @cathyharmon, Are you saying that removing line 196-197 in this Gemfile.lock

steps-ios-auto-provision/Gemfile.lock

Line 196 in 6d6b7be

BUNDLED WITH

will fix this issue?

The Gemfile.lock that you mention is part of this step.

[cathyharmon]

Hmm - can you try:

gem install bundler --force -v 2.0.1

I believe that should allow multiple versions to co-exist. Sorry about that

[cathyharmon]

@cain004 THANKS!

[moodagent]

Seems to work with 2.0.1 as well.

[mikeberlin]

So it seems this was a quick fix. Thank you for posting it!

Will this be resolved at a later date so we don't need to include this step?

[cathyharmon]

Yes, this should be used as a workaround.

[arielelkin]

fixed in 1.5.1

thanks!