cordova-node-xcode VS Xcodeproj

We are producing a white-label mobile app which also runs on Apple devices. It's part of our build chain to modify bespoken Xcode project files. Of great help is this node library which allows automating our build process which includes modifications to the Xcode project file: https://github.com/apache/cordova-node-xcode

Since the Xcode config is just a legacy plist file Xcode will recognize it if it is converted to json. So we just leave it as json right? Well I wish it was that easy but there is also Cordova and that has it’s own Xcode config parser that is actually quite bad cordova-node-xcode. It must have the legacy plist format and to make matters even worth it also needs the comments preserved.

[!] [!] Xcodeproj doesn't know about the following attributes {"productname"=>"wooappTests"} for the 'PBXNativeTarget' isa. If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new “““

Censorius is a small gem that generates deterministic and stable UUID paths for Xcodeproj. It's meant to be used either with CocoaPods or Xcake to reduce meaningless Xcode project file differences, and therefore make Xcode incremental builds after project generation shorter.

I’ve used the Cocoapods tool Xcodeproj to facilitate really nice Workflows that Xcode didn’t provide for me out of the box. I don’t need this in every project but when I do it’s a really nice API for manipulating the pbxproj files

https://github.com/CocoaPods/Xcodeproj