Cocoapods install suddenly fails

Bitrise Build Issue Report template

Description of the issue

iOS build suddenly started failing on CocoaPods install with this error:

/usr/local/lib/ruby/gems/2.4.0/gems/cocoapods-core-1.4.0/lib/cocoapods-core/yaml_helper.rb:62:in rescue in load_string' /usr/local/lib/ruby/gems/2.4.0/gems/cocoapods-core-1.4.0/lib/cocoapods-core/yaml_helper.rb:57:inload_string’
/usr/local/lib/ruby/gems/2.4.0/gems/cocoapods-core-1.4.0/lib/cocoapods-core/yaml_helper.rb:75:in load_file' /usr/local/lib/ruby/gems/2.4.0/gems/cocoapods-core-1.4.0/lib/cocoapods-core/lockfile.rb:40:infrom_file’
/usr/local/lib/ruby/gems/2.4.0/gems/cocoapods-1.4.0/lib/cocoapods/config.rb:199:in lockfile' /usr/local/lib/ruby/gems/2.4.0/gems/cocoapods-1.4.0/lib/cocoapods/command.rb:138:ininstaller_for_config’
/usr/local/lib/ruby/gems/2.4.0/gems/cocoapods-1.4.0/lib/cocoapods/command/install.rb:38:in run' /usr/local/lib/ruby/gems/2.4.0/gems/claide-1.0.2/lib/claide/command.rb:334:inrun’
/usr/local/lib/ruby/gems/2.4.0/gems/cocoapods-1.4.0/lib/cocoapods/command.rb:52:in run' /usr/local/lib/ruby/gems/2.4.0/gems/cocoapods-1.4.0/bin/pod:55:in<top (required)>’
/usr/local/bin/pod:22:in load' /usr/local/bin/pod:22:in'
Command failed, error: exit status 1

Previously this worked perfectly.


Where did the issue happen?

Hybrid stack, with both Android tools and Xcode 8

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

Cocoapods install 1.7.2


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

Build log

Sorry, this was my fault. Something happened while moving the code to a new repository. It’s alright now. Can you close this :)? Sorry for the inconvenience.

1 Like

No problem at all, glad to hear you managed to solve it @airmiha ! :wink:

Happy Building!