pod update pollutes the project #643

Closed
hartbit opened this Issue Nov 12, 2012 · 7 comments

3 participants

@hartbit

Running pod update with version 0.16.0.rc3 adds a reference to Pods.xconfig in the project, even if one already exists. It also adds a Copy Pods Resources build phase, even if one already exists. After several updates, the project gets polluted with these references and build phases.

@fabiopelosin
CocoaPods member

This is a known bug which I'm not able to reproduce. Can you report whether you experience it with a new test project so we can discern if the issue is related to a specific stack?

Not sure if @alloy has made some progress on it.

@hartbit

I can't reproduce it anymore: neither in a test project, nor in my own project. It does seem like a very slippery bug. I'll try to see what caused it.

@fabiopelosin
CocoaPods member

:-(

@hartbit

I don't have time at work to test this, but could it come from the Pods project not compiling successfully? I was messing around with the cocos2d podspec when I saw the problem.

@fabiopelosin
CocoaPods member

I think that it is related to the rewrite of xcodeproj (the gem responsible of reading and writing Xcode projects). We detect if you project is already integrated by looking if the library for the target is already present in the frameworks build phases of your target. Somehow this check is failing in the rc, however I'm not sure where is the bug.

Did you change your stack (Ruby version, RVM) during the experiments with the cocos2d gem?

@alloy alloy closed this in 9eddb38 Nov 14, 2012
@alloy
CocoaPods member

Released as 0.16.0.rc5.

@hartbit

Über thanks!

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