Summary: from a fresh install of cocopods, tried to do 'pod install'. I am on the newest version of xcode (7.3) and OSX 10.11.4
curl -sSL https://get.rvm.io | bash -s stable --ruby
source /Users/blah/.rvm/scripts/rvm
gem install cocoapods
pod setup
pod install
Install all pod dependencies correctly.
Crash
/Users/blah/.rvm/gems/ruby-2.3.0/bin/pod install
CocoaPods : 0.39.0
Ruby : ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15]
RubyGems : 2.5.1
Host : Mac OS X 10.11.4 (15E65)
Xcode : 7.3 (7D175)
Git : git version 2.6.4 (Apple Git-63)
Ruby lib dir : /Users/blah/.rvm/rubies/ruby-2.3.0/lib
Repositories : brion - https://github.com/brion/OGVKit-Specs.git @ 7e271579961bde8804b1a738e0d5380379467acb
master - https://github.com/CocoaPods/Specs.git @ 3822bbacf6f6784f102aabd71b7dfab34576a8b6
cocoapods-plugins : 0.4.2
cocoapods-search : 0.1.0
cocoapods-stats : 0.6.2
cocoapods-trunk : 0.6.4
cocoapods-try : 0.5.1
platform :ios, '7.0'
pod 'NSLogger'
NoMethodError - undefined method `to_ary' for #<Pod::Specification name="NSLogger">
Did you mean? to_query
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/resolver/lazy_specification.rb:14:in `method_missing'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/resolver.rb:64:in `flatten'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/resolver.rb:64:in `block in resolve'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/resolver.rb:63:in `tap'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/resolver.rb:63:in `resolve'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/installer/analyzer.rb:539:in `block in resolve_dependencies'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/user_interface.rb:59:in `section'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/installer/analyzer.rb:537:in `resolve_dependencies'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/installer/analyzer.rb:70:in `analyze'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/installer.rb:213:in `analyze'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/installer.rb:136:in `block in resolve_dependencies'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/user_interface.rb:59:in `section'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/installer.rb:135:in `resolve_dependencies'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/installer.rb:105:in `install!'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/command/project.rb:71:in `run_install_with_update'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/command/project.rb:101:in `run'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/claide-0.9.1/lib/claide/command.rb:312:in `run'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/lib/cocoapods/command.rb:47:in `run'
/Users/blah/.rvm/gems/ruby-2.3.0/gems/cocoapods-0.39.0/bin/pod:44:in `<top (required)>'
/Users/blah/.rvm/gems/ruby-2.3.0/bin/pod:23:in `load'
/Users/blah/.rvm/gems/ruby-2.3.0/bin/pod:23:in `<main>'
/Users/blah/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `eval'
/Users/blah/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `<main>'
[!] Oh no, an error occurred.
Search for existing GitHub issues similar to yours:
https://github.com/CocoaPods/CocoaPods/search?q=undefined+method+%60to_ary%27+for+%23%3CPod%3A%3ASpecification+name%3D%22NSLogger%22%3E%0ADid+you+mean%3F++to_query&type=Issues
This issue has been opened over 20 times -- please search closed issues in the future: https://github.com/CocoaPods/CocoaPods/search?utf8=โ&q=undefined+method+%60to_ary%27+for+Did+you+mean%3F++to_query&type=Issues. You can either use a ruby version < 2.3 or upgrade to the CocoaPods 1.0 betas.
Thank you for getting back to me segiddins.
The reason why i took the time to open the issue was because when i followed the instructions at the end of the error:
Search for existing GitHub issues similar to yours:
https://github.com/CocoaPods/CocoaPods/search?q=undefined+method+%60to_ary%27+for+%23%3CPod%3A%3ASpecification+name%3D%22NSLogger%22%3E%0ADid+you+mean%3F++to_query&type=Issues
There weren't any listed.
As a suggestion, maybe it could provide the existing search as well as a truncated issue so that it gets more search hits. This way the user is less likely to think that they are helping by posting, and get to the solution quickly.
For those of you following along at home, in April 2016, rvm updated their stable version to 2.3 which broke the ability to install cocoapods. Then when you try to build you will get an error, which will take you to the internet, and you will find one of the many threads of people complaining about this issue and not being able to build cocoapods. After some digging you will see the two recommendations (which the nice gentleman listed for me here) of
1) installing cocopods beta (which i had done in the past and all hell had broken loose so lets skip this option)
2) use a ruby version < 2.3
curl -sSL https://get.rvm.io | bash -s stable --ruby
source /Users/blah/.rvm/scripts/rvm
rvm install 2.2.2
rvm use 2.2.2
rvm gemset create rails2.2.2
gem install cocoapods
pod setup
pod install
@justlikealltherest please try and keep things civil in issues, and the cursing to a minimum -- it doesn't really contribute to a comfortable environment.
@segiddins thanks again for your help. please pardon my language. cocoapods just knows how to get going. I appreciate you getting back to me so promptly.
@justlikealltherest sorry, I don't want language like this on our public message board. It's awesome that you're passionate - but it's not how we want to have people participate ๐
So I've edited out some of the more explicit stuff, but left the useful gold ๐ฐ
@orta no problem, I understand. For those of you playing along at home, the PROGRAMMERS GONE WILD: TOO HOT FOR GITHUB EDITION (UNCENSORED) can be found here http://pastebin.com/dZmujxmK
Most helpful comment
@justlikealltherest sorry, I don't want language like this on our public message board. It's awesome that you're passionate - but it's not how we want to have people participate ๐