Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Original project.pbxproj serialized as XML instead of OpenStep format #613

Closed
jeanregisser opened this Issue · 2 comments

2 participants

@jeanregisser

After running pod install, I noticed the original project.pbxproj was serialized as XML instead of the OpenStep format.

One of the consequences is that using agvtool to bump the version number fails (because it sadly expects the OpenStep format):

$ agvtool new-version -all "123"
Setting version of project DummyProject to: 
    123.

Also setting CFBundleVersion key (assuming it exists)

Updating CFBundleVersion in Info.plist(s)...

Cannot find "DummyProject.xcodeproj/../             <key>INFOPLIST_FILE</key>"

With pod install --no-integrate the original pbxproj serialization is of course preserved.

I've seen that behavior in the past with other versions of CocoaPods / Xcodeproj but couldn't always reproduce it.
But now on my system, it's always the case with CocoaPods 0.16.0.rc2 and Xcodeproj 0.4.0.rc2.

Is it possible to preserve the original serialization format?

Stack

   CocoaPods : 0.16.0.rc2
        Ruby : ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin12.2.0]
    RubyGems : 1.8.24
        Host : Mac OS X 10.8.2 (12C60)
       Xcode : 4.5.1 (4G1004)
Ruby lib dir : /Users/jean/.rvm/rubies/ruby-1.9.3-p194/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ 9a7a71cb98497329a195f28a908ad6307908f85d
@alloy
Owner

Unfortunately it is not possible. The plist API only allows OpenStep format reading, not writing. The reason you probably not noticed it every time is that once you change something in your xcode project, Xcode will save it again in the OpenStep format. So in your case the workaround is to have Xcode save something after a pod install.

@alloy alloy closed this
@alloy
Owner

Released as 0.16.0.rc5.

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.