Cocoapods: undefined method `map' for nil:NilClass (NoMethodError) Did you mean? tap

Created on 17 Jan 2019  Â·  15Comments  Â·  Source: CocoaPods/CocoaPods

Report

What did you do?

Run pod install or pod update

What did you expect to happen?

pod dependencies get uploaded

What happened instead?

got following error message:

/Library/Ruby/Gems/2.3.0/gems/gh_inspector-1.1.3/lib/gh_inspector/sidekick.rb:95:in `parse_results': undefined method `map' for nil:NilClass (NoMethodError)
Did you mean?  tap
    from /Library/Ruby/Gems/2.3.0/gems/gh_inspector-1.1.3/lib/gh_inspector/sidekick.rb:34:in `search'
    from /Library/Ruby/Gems/2.3.0/gems/gh_inspector-1.1.3/lib/gh_inspector/inspector.rb:68:in `search_query'
    from /Library/Ruby/Gems/2.3.0/gems/gh_inspector-1.1.3/lib/gh_inspector/inspector.rb:62:in `search_exception'
    from /Library/Ruby/Gems/2.3.0/gems/cocoapods-1.5.3/lib/cocoapods/user_interface/error_report.rb:119:in `search_for_exceptions'
    from /Library/Ruby/Gems/2.3.0/gems/cocoapods-1.5.3/lib/cocoapods/command.rb:67:in `report_error'
    from /Library/Ruby/Gems/2.3.0/gems/claide-1.0.2/lib/claide/command.rb:396:in `handle_exception'
    from /Library/Ruby/Gems/2.3.0/gems/claide-1.0.2/lib/claide/command.rb:337:in `rescue in run'
    from /Library/Ruby/Gems/2.3.0/gems/claide-1.0.2/lib/claide/command.rb:324:in `run'
    from /Library/Ruby/Gems/2.3.0/gems/cocoapods-1.5.3/lib/cocoapods/command.rb:52:in `run'
    from /Library/Ruby/Gems/2.3.0/gems/cocoapods-1.5.3/bin/pod:55:in `<top (required)>'
    from /Users/xxx/.gem/ruby/2.3.0/bin/pod:22:in `load'
    from /Users/xxx/.gem/ruby/2.3.0/bin/pod:22:in `<main>'

CocoaPods Environment

### Stack

   CocoaPods : 1.5.3
        Ruby : ruby 2.3.7p456 (2018-03-28 revision 63024) [universal.x86_64-darwin17]
    RubyGems : 2.5.2.3
        Host : Mac OS X 10.13.6 (17G65)
       Xcode : 10.1 (10B61)
         Git : git version 2.19.2
Ruby lib dir : /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ 03d0a95c316ba6036f120f66c12a1eed23786dd6

### Installation Source

Executable Path: /usr/local/bin/pod

### Plugins

cocoapods-deintegrate : 1.0.2
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.0
cocoapods-stats       : 1.0.0
cocoapods-trunk       : 1.3.0
cocoapods-try         : 1.1.0

Most helpful comment

ah gem update xcodeproj fixes the problem for me

All 15 comments

This is an issue within an issue. The tool is trying to find similar issue and it fails.

I am moving this to the corresponding GH repo.

Actually I can't can you please file the issue here https://github.com/orta/gh_inspector/issues

Actually this looks just like https://github.com/orta/gh_inspector/issues/12

Yes!

@dnkoutso it looks like Cocoapods is passing in a string that's too long which is making it fail.

  1. Is there anything that can be done to prevent that?
  2. Why is this causing pod install and pod update to fail?

@chshapiro My gut feeling is that you are getting a different crash and while gh_inspector tries to find similar errors for you it fails and crashes _again_.

Can you modify your own gh_inspector gem to skip this check and then post here to see what the real underlying crash is?

@chshapiro I will re-open this issue once this is done!

@chshapiro for context, what you are seeing is a crash on the code that _handles crashes_ - when CocoaPods crashes, the exception is caught and gh_inspector searches for issues on Github that look similar to the error, in order to help the user find other issues that may be relevant.

This doesn't mean that it's causing pod install or pod update to fail, because by that point it had already failed.

is there no resolution here? I'm having same issue

ah gem update xcodeproj fixes the problem for me

issue is tracked here https://github.com/orta/gh_inspector/issues/12 no resolution yet. PRs welcome!

Thank you. My previous comment fixed the issue

If updating Xcodeproj fixed the issue, it was most likely this https://github.com/CocoaPods/CocoaPods/issues/7835

Yes most likely. I had a different pods installation where i had to manually edit the xcodeproj to remove the sections causing the problem.

The same issue occurred to me when }; was missing in .xcodeproj file. After fixing this the Cocopoads started working again.

Was this page helpful?
0 / 5 - 0 ratings