Skip to content

pod repo push failure after xcodeproj / fourflusher updates  #5445

@pkordal

Description

@pkordal

Command

/usr/local/bin/pod repo push private_specs_repo PROJECT.podspec --allow-warnings

Report

There is an issue when we want pushing pod spec to our private pod spec repo.

Our Gemfile has traditionally only one gem -

gem 'cocoapods', '1.0.0'

Before each work with cocoa pods we do gem update.

Few days ago problem mentioned in this report started occurring after versions of 2 gems were bumped
xcodeproj 1.0.0 -> 1.1.0
fourflusher 0.3.0 -> 0.3.1

As far as I checked there is some issue with Ruby's autoload in cocoapods/validator.rb.

Stack

   CocoaPods : 1.0.0
        Ruby : ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]
    RubyGems : 2.0.14.1
        Host : Mac OS X 10.11.5 (15F34)
       Xcode : 7.3.1 (7D1014)
         Git : git version 2.7.4 (Apple Git-66)
Ruby lib dir : /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib
Repositories :
               source - ssh://git@ourRepo @ 5b52ad5422ee5a76b16bf14a5e9bb58f2c0a7429

Plugins

cocoapods-deintegrate : 1.0.0
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.0
cocoapods-stats       : 1.0.0
cocoapods-trunk       : 1.0.0
cocoapods-try         : 1.0.0

Error

LoadError - cannot load such file -- fourflusher
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/validator.rb:717:in `xcodebuild'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/validator.rb:478:in `block in build_pod'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/user_interface.rb:144:in `message'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/validator.rb:477:in `build_pod'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/validator.rb:274:in `block in perform_extensive_analysis'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/validator.rb:263:in `each'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/validator.rb:263:in `perform_extensive_analysis'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/validator.rb:81:in `validate'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/command/repo/push.rb:126:in `block in validate_podspec_files'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/command/repo/push.rb:120:in `each'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/command/repo/push.rb:120:in `validate_podspec_files'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/command/repo/push.rb:65:in `run'
/Library/Ruby/Gems/2.0.0/gems/claide-1.0.0/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/lib/cocoapods/command.rb:50:in `run'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.0.0/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'

I saw @neonichu released fourflusher 0.3.1 few days ago. Maybe there is some issue with it?
I am not Ruby specialist yet so it is hard to me giving more support.

Update:
Lowering fourflusher in version 0.3 does the job until next gem update.

Best,
Paweł

Metadata

Metadata

Assignees

Labels

s2:confirmedIssues that have been confirmed by a CocoaPods contributor

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions