@Lumialxk
Yesterday I had a very similar thing. Just as my project.pbxproj file was in plist format, it differs in that I did not receive the message File 'project.pbxproj' is broken . Instead, a problem arose for me through a merge conflict. Where the conflict was in the project.pbxproj file. There was one conflict, and that was the entire contents of the file. In other words, there were two versions of the file. One on my new branch, where it was in plist format. And one on our base branch, where it was in the usual JSON format. In any case, this is similar to what you see.
It is important to note that both pre-merge branches work with Xcode. Xcode did not seem to have a problem with the project.pbxproj file formatted by plist.
I solved the problem by doing git reset --hard HEAD to discard the merge attempt, this brought me back to the point where I had a branch with the plist project.pbxproj file that I could create and run without problems. Then I selected a random build setting (code signing), changed its value and then changed it (i.e. I just “touched” it to make Xcode change it). Then I built a project. And then reopened the project.pbxproj file in a text editor. After it “touched” the file, it returned to its normal format; there is no longer a plist format.
There was a smooth swim.
Credit comes to my colleague for offering a “sensory” approach.
I am not sure what caused the problem. Here are some details about my setup:
I am running Xcode 7.3 (so I do not think this had anything to do with 7.3.1). I recently upgraded from Cocoapods 0.39.0 to 1.0. I think this is a criminal. I ran into problems when creating some modules with 1.0, which I solved, forcing to use 0.39.0 as follows:
pod _0.39.0_ install
pod _0.39.0_ update
Hope this helps!
Alfie hanssen
source share