Closed Amnesthesia closed 7 years ago
Odd. I can reproduce the same problem over here.
Try this:
potion new sorry
cd sorry
rake clean:all
rm Gemfile.lock
At this point, open your Gemfile in the editor of choice (the correct answer is Vim).
Force cocoapods to bind to 0.37.2 by adding this on line 4:
gem "cocoapods", "0.37.2"
Your gems will be loaded in this order: rake
, cocoapods
, motion-cocoapods
.
Then
bundle
rake pod:install
rake
You'll see a warning that cocoapods 0.38.0 is available, but you'll be targeting 0.37.2.
Cocoapods 0.38.0 just came out a few days ago. I'm guessing motion-cocoapods
is perhaps getting tripped up? I haven't looked at all, but it's fun to blame others!
Strange
Seems we're not alone:
This problem has been resolved. Just make sure you have the latest version of motion-cocoapods installed.
Hiya!
I'm trying to get started with redpotion, but can't get past the initial setup. I'm on Yosemite, xcode 6.3 and everything else is set up fine (rake'ing a normal ruby-motion project works fine) but as soon as I've created the redpotion project (by the way, the documentation still has 'redpotion create' instead of the rails-like 'redpotion new ') and I try to rake it, it fails creating .a libraries (or finding them?) for the
vendor/Pods
I've tried to
rake clean
andrake newclear
hoping it'd be that easy, but with no luck. Opening the .xcodeproj for Pods in Xcode and building it works fine as well. I thought, at first, that it might be that I'm on a case-sensitive HFS partition which has caused me trouble before (coming from Linux, when I installed I thought 'why wouldnt it be case sensitive?' and thats where that mistake is from) but the issue remains the same even after doing it all in a case sensitive sparsebundle.Here's my stacktrace:
Any idea of what may be causing this? I've also tried downgrading the cocoapods gem, building in Xcode first, and so on - no luck.