How do you find typos (syntax errors) in an improperly formatted plist (property list) file, especially when Xcode provides absolutely no detail about badly formed XML? I often see plist files with a thousand or more lines of text! In this article, I’ll show you how to fix plist bugs — and do a few other things — by using the little-known plutil command line tool.
How many times have you seen the following error message, shown below in textual and graphical format, when doing a build?
|
1 |
: couldn't parse contents of '/path/to/project/projectName/projectName/Info.plist': The data couldn't be read because it isn't in the correct format. |
Jump straight to the fix or take a minute to read a little background.
Continue reading “Using the ‘plutil’ utility to fix improperly-formatted Xcode plist files”