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 for Bug 55356 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 21611 [details]
Sample Project/Before and after images
Tested on Android 4.4
When using a master detail page and updating the text for the label via binding it loses horizontal formatting/vertical formatting.
1. Look at master, see text in pink centered.
2. Look at detail text is centered properly
2. Press "ADD ITEM" in top right
3. Look at detail text is centered properly and updated
4. Look at master and text in pink box is no longer centered("Item Count" is still formatted properly)
I am able to reproduce this issue with the attached project. I am confirming this report and team will investigate further.
This is only occurring on Android. When the Master page is closed and the Label it updated, the Label loses its TextAlignment. However if the Label is updated with the Master page open, it behaves as expected. This makes this issue similar, if not the same as bug 55359.
Interestingly though, with Forms 2.3.4 the issue does not occur the first time the Label is updated, only subsequent times. However with 188.8.131.52 the issue occurs every time.
### Version Tests
Also stil on 184.108.40.206-pre3
*** Bug 57755 has been marked as a duplicate of this bug. ***