iOS Auto-provision step started failing

Question & Answer Builds
1

Bitrise Build Issue Report template

Description of the issue

iOS builds are now failing in the iOS ios-auto-provision step (1.5.0)
Please describe the issue here

Environment:

Where did the issue happen?

If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)

Xcode 11.3.x, on macOS 10.14.6 (Mojave)

Which build Step causes the issue and which version of the step?

| id: ios-auto-provision |
| version: 1.5.0 |
| collection: GitHub - bitrise-io/bitrise-steplib: New Bitrise StepLib |
| toolkit: bash |
| time: 2020-01-14T16:36:51Z |

https://github.com/bitrise-steplib/steps-ios-auto-provision/issues/106

Reproducibility

  • 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. : YES/NO
  • Does the issue happen sporadically, or every time? :
  • Does upgrading the build Step to the latest version help? : YES/NO
  • When did the issue start? :

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.

Local reproduction: Linux / Android (docker based) stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( Bitrise CLI )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: Redirecting… .

Build log

Can provide build log url if necessary

2

Same problem here. Happened after the stack was updated to Xcode 11.3.1

3

Also affected by this issue, firs occurred Yesterday 17:12 CET

4

Yes issue appeared after stack was updated to Xcode 11.3.1 - there are work-arounds discussed on the github issue on the step repository:

https://github.com/bitrise-steplib/steps-ios-auto-provision/issues/106

As well as mention of fix in progress.

1 Like
5

Same here:

$ bundle install

/Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/site_ruby/2.6.0/rubygems.rb:275:in `find_spec_for_exe’: Could not find ‘bundler’ (1.17.3) required by your /var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise033925944/step_src/Gemfile.lock. (Gem::GemNotFoundException)

To update to the latest version installed on your system, run bundle update --bundler.

To install the missing version, run gem install bundler:1.17.3

from /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/site_ruby/2.6.0/rubygems.rb:294:in `activate_bin_path’

from /Users/vagrant/.rbenv/versions/2.6.5/bin/bundle:23:in `’

bundle install failed

6

Hi everyone!

Really sorry about this inconvenience! We are aware of the issue with the step and should roll out a fix soon. In the meantime, it’s best to roll back to version 1.5.0 of ios-auto-provision and also include a script step before it with the contents gem install bundler --force -v 1.17.3 . If this workaround fails to resolve the issue, please let us know! We should have a fix deployed soon.

7

Hey again! :wave: We’re happy to report that the latest ios-auto-provision step release 1.5.2 should resolve any issues related to bundler that have been occurring with the step. You should be able to remove any workarounds that are in place and simply use the latest version of the step to use it as intended.

2 Likes
8

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