pod repo lint started printing a backtrace

[kylef]

Report

• What did you do?

$ pod repo lint master

• What did you expect to happen?

To lint the master repository

• What happened instead?

I was shown this backtrace.

Stack

   CocoaPods : 0.34.0.rc1
        Ruby : ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin14]
    RubyGems : 2.0.14
        Host : Mac OS X 10.10 (14A329f)
       Xcode : 6.0 (6A313)
Ruby lib dir : /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib
Repositories : artsy - https://github.com/artsy/Specs @ e91065751b5f7d9dba3d1bc7a6e407015b5b117e
               master - https://github.com/CocoaPods/Specs.git @ cf71bc463a70e69134e227aba60074946870204b

Plugins

cocoapods-docstats : 0.0.1
cocoapods-packager : 0.4.0
cocoapods-plugins  : 0.3.1
cocoapods-trunk    : 0.2.0
cocoapods-try      : 0.4.0

Error

TypeError - no implicit conversion of nil into Array
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter/analyzer.rb:135:in `-'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter/analyzer.rb:135:in `validate_attribute_hash_keys'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter/analyzer.rb:114:in `validate_attribute_value'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter/analyzer.rb:59:in `block in check_attributes'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter/analyzer.rb:52:in `each'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter/analyzer.rb:52:in `check_attributes'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter/analyzer.rb:15:in `analyze'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter.rb:123:in `block (2 levels) in perform_all_specs_analysis'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter.rb:119:in `each'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter.rb:119:in `block in perform_all_specs_analysis'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter.rb:118:in `each'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter.rb:118:in `perform_all_specs_analysis'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/specification/linter.rb:51:in `lint'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/source/health_reporter.rb:88:in `lint_spec'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/source/health_reporter.rb:53:in `block (2 levels) in analyze'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/source/health_reporter.rb:50:in `each'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/source/health_reporter.rb:50:in `block in analyze'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/source/health_reporter.rb:49:in `each'
/Users/kylef/gems/gems/cocoapods-core-0.34.0.rc1/lib/cocoapods-core/source/health_reporter.rb:49:in `analyze'
/Users/kylef/gems/gems/cocoapods-0.34.0.rc1/lib/cocoapods/command/repo.rb:129:in `block in run'
/Users/kylef/gems/gems/cocoapods-0.34.0.rc1/lib/cocoapods/command/repo.rb:121:in `each'
/Users/kylef/gems/gems/cocoapods-0.34.0.rc1/lib/cocoapods/command/repo.rb:121:in `run'
/Users/kylef/gems/gems/claide-0.7.0/lib/claide/command.rb:271:in `run'
/Users/kylef/gems/gems/cocoapods-0.34.0.rc1/lib/cocoapods/command.rb:48:in `run'
/Users/kylef/gems/gems/cocoapods-0.34.0.rc1/bin/pod:33:in `<top (required)>'
/Users/kylef/gems/bin/pod:23:in `load'
/Users/kylef/gems/bin/pod:23:in `<main>'

[kylef]

Fixed, the specs that caused this crash are these:

-> Incompatible `type` key(s) with `http` primary key for `source` attribute
  - Calabash (0.10.0.pre8, 0.9.169, 0.9.168, 0.9.168.pre4, 0.9.167, 0.9.166, 0.9.165, 0.9.163, 0.9.163.pre4, 0.9.163.pre3, 0.9.162)
  - Shark-SDK (2.3.4)
  - smc-runtime (6.3.0)

[fabiopelosin]

👍 I was going to fix it as well to troubleshoot another issue and luckily found this!