Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
When trying to save settings via the Xamarin Studio Project Settings editor that will be stored in the info.plist that is read only at that moment xamarin studio will show up a crash report.
Step to reproduce:
1. Make sure the info.plist file is read only
2. Edit some settings that will be stored in the info.plist file for you iOS app
3. Click OK
>> Xamarin studio will now come up with a crash report dialog and the settings wont be saved.
it doesn't crash, it just shows an exception dialog
Well allright, but it's also not saving.
And sometimes it actually does crash, I would expect a dialog asking me if I would like to make the file writable.
Mike: how does the text editor normally handle read-only files? And where can I find the code?
SourceEditorView.cs:203 - ReadOnlyCheckDelegate (but that's not from me)
ah forget about the ReadOnlyCheckDelegate - it's not important in your case.
fixed in git master
Today we have checked this issue with following builds :
XS 4.2.3(build 146)76e7c7f6ca0e59052f2bb29f8179313510977377
Now when we make changes in read-only info.plist file then it ask to convert it in writable and save it without any error.
Screencast : http://www.screencast.com/t/saGg6mEDf
Hence closing this issue.