Update my libraries #953

Merged
merged 2 commits into from Dec 31, 2012

5 participants

@soffes

No description provided.

soffes added some commits Dec 30, 2012
@soffes soffes Add SSPullToRefresh 1.0.2 e5373ef
@soffes soffes Update 1.0.2 SSToolkit spec.
Looks like someone else added this. I have just created the 1.0.2 tag, so it was probably failing before.
d79f806
@orta
CocoaPods member

Great, that looks good @soffes. Do you want commit access to be able to do this without PRs?

@orta orta merged commit ca64c32 into CocoaPods:master Dec 31, 2012

1 check failed

Details default The Travis build failed
@travisjeffery

The SSToolkit spec's currently messed right now since there's no 1.0.2 tag in the repo.

@keith
CocoaPods member

@soffes did say he created a 1.0.2 tag, it looks like he pushed the commit but not the tag refs. Also @fictorial may want to submit a new spec or talk to @soffes about his changes in the previous 1.0.2 spec.

@soffes

Fixed.

@keith
CocoaPods member

Awesome thanks!

@cabbiepete

Since the update to this spec I can no longer install it. It fails on the post_install resources build saying

xcodebuild: error: 'SSToolkit.xcodeproj' does not exist.
[!] Failed to generate SSToolkit resources bundle

Any ideas?

CocoaPods member

Try cleaning out your ~/Library/Caches/CocoaPods folder and try to run pod install --verbose again and toss the output in here.

Cleaned out as above then ran with --verbose here's the output (there's more above that succeeded but seems irrelevant let me know if its useful). Interestingly the only thing added to ~/Library/Caches/CocoaPods folder is a Git/7f8089a4... folder which is a repo for another pod I am using. I.e. the git repo for SSToolKit isn't in there which would explain why SSToolKit.xcodeproj isn't found but not as to why it isn't downloaded.

Generating SSToolkit resources bundle

Build settings from command line:
    CONFIGURATION_BUILD_DIR = ../Resources

xcodebuild: error: 'SSToolkit.xcodeproj' does not exist.
[!] Failed to generate SSToolkit resources bundle

/Users/cabbiepete/.cocoapods/master/SSToolkit/1.0.2/SSToolkit.podspec:24:in `block in post_install'
/Users/cabbiepete/.cocoapods/master/SSToolkit/1.0.2/SSToolkit.podspec:20:in `chdir'
/Users/cabbiepete/.cocoapods/master/SSToolkit/1.0.2/SSToolkit.podspec:20:in `post_install'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/installer.rb:157:in `block (2 levels) in run_post_install_hooks'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/installer.rb:156:in `each'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/installer.rb:156:in `block in run_post_install_hooks'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/installer.rb:155:in `each'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/installer.rb:155:in `run_post_install_hooks'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/installer.rb:127:in `block (2 levels) in install!'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/user_interface.rb:77:in `message'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/installer.rb:125:in `block in install!'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/user_interface.rb:37:in `section'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/installer.rb:112:in `install!'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/command/install.rb:46:in `run_install_with_update'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/command/install.rb:51:in `run'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/lib/cocoapods/command.rb:75:in `run'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/gems/cocoapods-0.16.1/bin/pod:16:in `<top (required)>'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/bin/pod:19:in `load'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/bin/pod:19:in `<main>'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/bin/ruby_noexec_wrapper:14:in `eval'
/Users/cabbiepete/.rvm/gems/ruby-1.9.3-p327/bin/ruby_noexec_wrapper:14:in `<main>'

If I revert the podspec back to before this commit it works fine (although that's expected I guess).

CocoaPods member

What's in the yourproject/Pods/SSToolkit folder?

pwd
~/myproject/Pods/SSToolkit
➜ SSToolkit git:(develop) ✗ ls -la
total 24
drwxr-xr-x 7 cabbiepete staff 238 3 Sep 14:47 .
drwxr-xr-x 22 cabbiepete staff 748 18 Jan 11:46 ..
drwxr-xr-x 20 cabbiepete staff 680 3 Sep 14:47 Assets
-rw-r--r-- 1 cabbiepete staff 1059 3 Sep 14:47 LICENSE
-rw-r--r-- 1 cabbiepete staff 1886 3 Sep 14:47 Readme.markdown
drwxr-xr-x 104 cabbiepete staff 3536 3 Sep 14:47 SSToolkit
-rw-r--r-- 1 cabbiepete staff 1023 3 Sep 14:47 SSToolkit.podspec

CocoaPods member

FIX

Ok so the issue is that you still have files from the old spec that pointed to this repo instead of Sam's. You can tell because you have the Assets folder instead of Resources (IMO this shouldn't have been merged).

You should be able to fix it by removing the pod 'SSToolkit' ... from your Podfile run pod install so it cleans up all the old SSToolkit stuff, add it back to your podfile and install again. That should clean up all the crap. (You may want to clean out that Caches folder again in-between)

Yep that fixed it. And IMO I agree another version would have been much better i.e. 1.0.3 I really didn't expect something to change when I changed nothing. Anyways issue and fix documented here for others now thanks for your help.

CocoaPods member

Awesome! Let us know if you need anything else!

So do need anything from me?

Don't think so all sorted. Hopefully not too many others have the same issue but if they do hopefully they find this. Thanks again for the toolkit :-).

CocoaPods member

@soffes the issue is that the fork that used to be 1.0.2 changed the Resources folder to Assets (apparently to fix some simulator) issue and it had to be cleaned about because yours was looking for resources instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment