fastlane: xcode_install not working anymore

xcode_install suddenly stopped working, I believe it was after I updated Fastlane, but I’m not sure. I’m currently running Fastlane 1.57.0. The error log:

14:09:39]: ---------------------------
[14:09:39]: --- Step: xcode_install ---
[14:09:39]: ---------------------------
/Users/sds/.rvm/rubies/ruby-2.1.2/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:2112:in `raise_if_conflicts': Unable to activate xcode-install-1.2.5, because spaceship-0.19.3 conflicts with spaceship (= 0.15.1) (Gem::ConflictError)
    from /Users/sds/.rvm/rubies/ruby-2.1.2/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:1280:in `activate'
    from /Users/sds/.rvm/rubies/ruby-2.1.2/lib/ruby/site_ruby/2.1.0/rubygems.rb:198:in `rescue in try_activate'
    from /Users/sds/.rvm/rubies/ruby-2.1.2/lib/ruby/site_ruby/2.1.0/rubygems.rb:195:in `try_activate'
    from /Users/sds/.rvm/rubies/ruby-2.1.2/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:126:in `rescue in require'
    from /Users/sds/.rvm/rubies/ruby-2.1.2/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:39:in `require'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/actions/xcode_install.rb:13:in `run'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/runner.rb:143:in `block (2 levels) in execute_action'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/runner.rb:129:in `block in execute_action'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/runner.rb:128:in `chdir'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/runner.rb:128:in `execute_action'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/fast_file.rb:149:in `method_missing'
    from Fastfile:15:in `block (2 levels) in parsing_binding'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/runner.rb:49:in `call'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/runner.rb:49:in `block in execute'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/runner.rb:46:in `chdir'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/runner.rb:46:in `execute'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/lib/fastlane/command_line_handler.rb:30:in `handle'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/bin/fastlane:38:in `block (2 levels) in run'
    from /Users/sds/.rvm/gems/ruby-2.1.2@global/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Users/sds/.rvm/gems/ruby-2.1.2@global/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Users/sds/.rvm/gems/ruby-2.1.2@global/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
    from /Users/sds/.rvm/gems/ruby-2.1.2@global/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
    from /Users/sds/.rvm/gems/ruby-2.1.2@global/gems/fastlane_core-0.36.1/lib/fastlane_core/ui/fastlane_runner.rb:23:in `run!'
    from /Users/sds/.rvm/gems/ruby-2.1.2@global/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/bin/fastlane:150:in `run'
    from /Users/sds/.rvm/gems/ruby-2.1.2/gems/fastlane-1.57.0/bin/fastlane:156:in `<top (required)>'
    from /Users/sds/.rvm/gems/ruby-2.1.2/bin/fastlane:23:in `load'
    from /Users/sds/.rvm/gems/ruby-2.1.2/bin/fastlane:23:in `<main>'
    from /Users/sds/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `eval'
    from /Users/sds/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `<main>'

I’ve tried calling gem update and gem cleanup but without any luck.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 22 (11 by maintainers)

Commits related to this issue

Most upvoted comments

I experimented a bit on this problem today and I think there’s a somewhat feasible solution, which requires a little bit of extra work for folks wanting to install xcode-install on a fresh system.

I have created a fork of domain_name without the native dependency with a much higher patch version than the currently released one. Folks which do not want the native dependency can manually install that and then run the xcode-install installation using the --conservative flag and this will lead to the already installed fork being used, so no native extension is required. This is what people need to run for this:

curl -sL -O https://github.com/neonichu/ruby-domain_name/releases/download/v0.5.99999999/domain_name-0.5.99999999.gem
gem install domain_name-0.5.99999999.gem
gem install --conservative spaceship

In theory, we could let spaceship depend on this fork, but since the native dependency lies several transitive steps down the chain, it feels like too much effort to keep all those forks updated. I would add the slightly more complicated install process for first-time users to the xcode-install README to make the people who need it aware of it.

For most other folks, who previously installed the developer tools on their system, the regular gem install process will work just fine 👌

I feel like this is an OK solution to this annoying problem — @mfurtak, @KrauseFx do you see any issues with this?