Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

0.32.0 appears to break Development Pods in a Project #2050

Closed
kcharwood opened this Issue · 16 comments

5 participants

@kcharwood

It appears that 0.32.0 now has absolute paths for development pods, which is breaking our CI build as well as other developer builds when pulling down the latest.

Wanted to get this up now. Will follow up with more information as I have it.

@kcharwood

Previously, development pods were installed with a relative path:

screen shot 2014-04-15 at 11 37 42 am

Now, they have an absolute path:
screen shot 2014-04-15 at 11 37 16 am

@kcharwood

Looking through the changelog, I see #1042

Will take a look and make sure we are doing this correctly.

@fabiopelosin

This is a feature so... deal with it! No kidding :smile: you can easily fix your CI by specifying the paths as relative in your Podfile.

@kylef
Owner

Hmm, this sounds somewhat related to my fix for CocoaPods/Xcodeproj#118

CocoaPods/Xcodeproj@46a66dc Just I just remembered I did this commit and have't got merged yet :+1:

@kcharwood

Still investigating, but I updated my path to be:

:path => './ThirdPartyCode/UrbanAirship'

And re ran pod install, and it still is coming up with an absolute path.

@larsacus

Our original path in our podfile that broke CI was :path => 'ThirdPartyCode/UrbanAirship', which also looks like a relative path.

@kcharwood

@irrationalfab can you verify our comments above? Are we missing something, or is there a bug here?

Thanks

@fabiopelosin

Can you post the Podfile?

@fabiopelosin

I have removed the min version requirement from the specs repo for the time being so you can downgrade

@larsacus

Saw you just closed this. Do you still need the pod file?

@fabiopelosin

No, it should be fixed.. thanks!

@fabiopelosin

Can you try with CocoaPods 0.32.1?

@larsacus

Trying now

@alloy
Owner

Perfect. Thanks for the update!

@fabiopelosin

Ace!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.