Fix unstable reads for XCSchemeManagement
#758
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves: #756
Short description 📝
xcschememanagement.plist
file was resulting in differentXCSchemeManagement
objectsschemeUserState
from a dictionary to an array without sorting the dictionary keyXCSchemeManagement
arrays each time the plist was readXCSchemeManagement
>plist
) is most likely why this wasn't previously noticedSolution 📦
Test Plan 🛠️
xcschememanagement.plist
file remains unchanged by these changesNotes 📝
it's unclear why the
schemeUserState
is stored as an array, it's a candidate to be changed to dictionary in the next major release as it would be a breaking change to do so now without any compatibility accessors to maintain the same public API.