Fastlane install fails

gem install fastlane --verbose
fails because of a circular dependency error, this wasn’t an issue for the last few weeks. Any workarounds for this? I haven’t added any components to the circle file before this.

output log:

HEAD https://api.rubygems.org/api/v1/dependencies
    200 OK
    GET https://api.rubygems.org/api/v1/dependencies?gems=fastlane
    200 OK
    Getting SRV record failed: DNS result has no information for _rubygems._tcp.api.rubygems.org
    GET https://api.rubygems.org/quick/Marshal.4.8/fastlane-2.1.0.gemspec.rz
    200 OK
    GET https://api.rubygems.org/api/v1/dependencies?gems=activesupport,addressable,babosa,bundler,colored,commander,dotenv,excon,faraday,faraday-cookie_jar,faraday_middleware,fastimage,gh_inspector,google-api-client,highline,json,mini_magick,multi_json,multi_xml,multipart-post,plist,rubyzip,security,slack-notifier,terminal-notifier,terminal-table,word_wrap,xcode-install,xcodeproj,xcpretty,xcpretty-travis-formatter
    200 OK
    GET https://api.rubygems.org/api/v1/dependencies?gems=CFPropertyList,claide,googleauth,http-cookie,httpclient,hurley,i18n,memoist,mime-types,minitest,nanaimo,public_suffix,representable,retriable,rouge,spaceship,thread_safe,tzinfo,unicode-display_width
    200 OK
    GET https://api.rubygems.org/api/v1/dependencies?gems=credentials_manager,domain_name,jwt,logging,mime-types-data,os,signet,uber
    200 OK
    ERROR:  While executing gem ... (Gem::Resolver::Molinillo::CircularDependencyError)
        There is a circular dependency between credentials_manager and fastlane

gem install fastlane --verbose returned exit code 1

Action failed: gem install fastlane --verbose

Thanks

Just wondering, what version of credentials_manager are you using? I just noticed that all versions of 0.16.x were yanked from RubyGems and I wonder if this is related.

I got the same error starting last night and was using 0.16.2

I’m using 0.16.2, which is the default for the machine because I haven’t set it up as a dependency on my circle file.

This is being tracked by Fastlane here https://github.com/fastlane/fastlane/issues/7582

It looks like they may have a workaround as well.

1 Like