You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Xcode stores project schemes in a format that is different to format used by xcproj, more specifically it adds new lines when xcproj does not, order of actions is different, it adds empty blocks when xcproj does not. That leads to files content being completely overridden when changes are made either by Xcode or xcproj or even when the project is saved by xcproj without any chnages in schemes.
The same seems to happen with all other xml files, like workspace data.
Option 1. xcproj should match Xcode format to avoid unneeded changes. This may break on each Xcode update
Option 2. still override all the content of the file, but only when changes are made. This will be at least something, but still will have unneeded side effects when xcproj is used as helper by another tool, i.e. Sourcery
The text was updated successfully, but these errors were encountered:
What 🌱
Xcode stores project schemes in a format that is different to format used by xcproj, more specifically it adds new lines when xcproj does not, order of actions is different, it adds empty blocks when xcproj does not. That leads to files content being completely overridden when changes are made either by Xcode or xcproj or even when the project is saved by xcproj without any chnages in schemes.
The same seems to happen with all other xml files, like workspace data.
Example.
Xcode generated scheme:
xcrpoj generated scheme
Proposal 🎉
Option 1. xcproj should match Xcode format to avoid unneeded changes. This may break on each Xcode update
Option 2. still override all the content of the file, but only when changes are made. This will be at least something, but still will have unneeded side effects when xcproj is used as helper by another tool, i.e. Sourcery
The text was updated successfully, but these errors were encountered: