Skip to content

Conversation

@rolfbjarne
Copy link
Member

@jstedfast
Copy link
Member

Thanks for tackling this, @rolfbjarne

Copy link

@spouliot spouliot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are we sure the last entry wins (e.g. if used from Xcode) ?
or is it a best guess ?
it will solve the exception but it might not produce what's expected

@jstedfast
Copy link
Member

@spouliot in the reported case, both plist values are actually the same. But yea, I don't think we know - I think it's a best guess until we get a report where the values are different.

Since it's apparently a bug in Apple's web server, it probably won't last long.

@jstedfast
Copy link
Member

@rolfbjarne
Copy link
Member Author

@spouliot

are we sure the last entry wins

I tested it:

$ cat text.plist 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>key</key>
	<string>value</string>
	<key>key</key>
	<string>second value</string>
</dict>
</plist>
$ /usr/libexec/PlistBuddy -c "Print :key" ./text.plist 
second value

@rolfbjarne rolfbjarne merged commit 2029b17 into dotnet:master Dec 17, 2018
rolfbjarne added a commit to rolfbjarne/Xamarin.MacDev that referenced this pull request Dec 17, 2018
rolfbjarne added a commit to rolfbjarne/Xamarin.MacDev that referenced this pull request Dec 17, 2018
rolfbjarne added a commit that referenced this pull request Dec 17, 2018
rolfbjarne added a commit that referenced this pull request Dec 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants