Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: can't satisfy 'google-cloud-env (>= 1.6.0, < 2.0.0)', already activated 'google-cloud-env-2.1.0' #21788

Closed
4 tasks done
triplef opened this issue Jan 9, 2024 · 3 comments

Comments

@triplef
Copy link
Contributor

triplef commented Jan 9, 2024

New Regression Checklist

Regression Information

  • Breaking version: 2.219.0
  • Last working version: 2.218.0

Regression Description

After upgrading to 2.219.0 I’m getting this error when running fastlane:

can't satisfy 'google-cloud-env (>= 1.6.0, < 2.0.0)', already activated 'google-cloud-env-2.1.0' (Gem::LoadError)

This seems to be caused by #21777. How can I find out what is activating google-cloud-env-2.1.0?

/opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/rubygems/specification.rb:1452:in `block in activate_dependencies': can't satisfy 'google-cloud-env (>= 1.6.0, < 2.0.0)', already activated 'google-cloud-env-2.1.0' (Gem::LoadError)
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/rubygems/specification.rb:1444:in `each'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/rubygems/specification.rb:1444:in `activate_dependencies'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/rubygems/specification.rb:1426:in `activate'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/rubygems.rb:284:in `block in activate_bin_path'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/rubygems.rb:283:in `synchronize'
	from /opt/homebrew/Cellar/ruby/3.2.2_1/lib/ruby/3.2.0/rubygems.rb:283:in `activate_bin_path'
	from /Users/me/.gem/bin/fastlane:25:in `'

Environment

Cannot run fastlane env because of the above error.

@lacostej
Copy link
Collaborator

lacostej commented Jan 9, 2024

Do you run fastlane using a package manager? E:g. Bundler.

If not, can you try?
If yes, does bundle exec fastlane env works?

@triplef
Copy link
Contributor Author

triplef commented Jan 10, 2024

In this specific setup I’m currently not using a package manager, but I found out the problem seems to be with googleauth:

I had googleauth-1.9.1 installed, which depends on google-cloud-env (~> 2.1) and which clashes with the google-cloud-env (>= 1.6.0, < 2.0.0) dependency from fastlane. If I install googleauth-1.8.1 it works fine.

Maybe this dependency needs to be pinned to < 1.9?

require 'googleauth'

@triplef
Copy link
Contributor Author

triplef commented Jan 10, 2024

Using Bundler on another machine it actually works fine as it resolves googleauth to 1.8.1, so I guess this was just a local issue due to not using a package manager. Sorry for the noise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants