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.
MFA 4.2 RC4
Steps to reproduce:
Add a button to a layout
Double click the button to open the text/resource editor
Click the text box to have the text box gain focus
Press tab to switch to the resource
Edit the resource name
Click off the button to close the text boxes.
Save the file.
Expected (and MD behavior):
After clicking off the button, the button should show the resource in resource name format (@string/buttonA)
After saving the document, the button should update with the resource value ("Button")
After clicking off the button, the button *does* show the resource in resource name format (@string/buttonA)
After saving the document, the button *does not* update with the resource value, the button continues to show the resource name.
Workaround: close/reopen the .axml file
Marking as normal. While it will be frustrating to have to re-open the .axml file to correctly display the string values (and therefore the spacing/etc), there is a workaround and this issue does not manifest if you are using pre-existing string resources.
The string value should actually be shown when the resource is created, not when saving. This used to work.
Fixed in master (2bc4039075d3bf641e923102bd273dc3c6a231f9)
Verified fixed in MFA 4.2.0 RC5