Define version from dependency #908

Closed
m1imueller opened this Issue Mar 27, 2013 · 2 comments

Projects

None yet

3 participants

@m1imueller

i want use ZBarSDK in a project.

first i try to use the newest version from ZBarSDK (1.3.1) but something in the podspec is no wrong(i will create another issue).

then i try to use the version 1.2.2 and i use the following podfile

platform :ios, '6.0'
pod 'SSZipArchive'
pod 'ZBarSDK', '1.2.2'

Problem:

pod install try to use ZBarSDK 1.3.1

Error

wrong number of arguments (0 for 1)
/Users/mmueller/.cocoapods/master/ZBarSDK/1.3.1/ZBarSDK.podspec:37:in `post_install'
/Users/mmueller/.cocoapods/master/ZBarSDK/1.3.1/ZBarSDK.podspec:37:in `_eval_podspec'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/specification.rb:59:in `initialize'
/Users/mmueller/.cocoapods/master/ZBarSDK/1.3.1/ZBarSDK.podspec:1:in `new'
/Users/mmueller/.cocoapods/master/ZBarSDK/1.3.1/ZBarSDK.podspec:1:in `_eval_podspec'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/specification.rb:27:in `eval'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/specification.rb:11:in `_eval_podspec'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/specification.rb:27:in `from_file'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/source.rb:71:in `specification'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/specification/set.rb:94:in `specification'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/source.rb:85:in `search'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/specification.rb:11:in `find'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/source.rb:80:in `each'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/source.rb:80:in `find'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/source.rb:80:in `search'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/source.rb:158:in `search'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/source.rb:158:in `select'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/source.rb:158:in `search'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/resolver.rb:172:in `find_cached_set'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/resolver.rb:192:in `find_dependency_specs'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/user_interface.rb:77:in `message'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/resolver.rb:191:in `find_dependency_specs'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/resolver.rb:186:in `each'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/resolver.rb:186:in `find_dependency_specs'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/resolver.rb:92:in `resolve'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/user_interface.rb:37:in `section'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/resolver.rb:90:in `resolve'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/resolver.rb:89:in `each'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/resolver.rb:89:in `resolve'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/installer.rb:186:in `specs_by_target'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/installer.rb:101:in `install!'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/user_interface.rb:37:in `section'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/installer.rb:100:in `install!'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/command/install.rb:46:in `run_install_with_update'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/command/install.rb:51:in `run'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/lib/cocoapods/command.rb:75:in `run'
/Library/Ruby/Gems/1.8/gems/cocoapods-0.16.4/bin/pod:16
/usr/bin/pod:23:in `load'
/usr/bin/pod:23
@fabiopelosin
CocoaPods member
@alloy
CocoaPods member

This looks to be related to CocoaPods/Specs@41bdfe5.

Please re-open if that does not fix the issue.

@alloy alloy closed this Mar 30, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment