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 we dynamically change the content of an invisible ContentView, it does not become visible with the next IsVisible = true.
See the following project https://github.com/philippd/ContentView-Bug.git which shows this issue.
- Tap on Update
- Tap on Hide
- Tap on Update again
-> The content is not visible
- Tap on Update
-> The content becomes visible
Workaround: If the ContentView is set to visible before changing the content, everything works fine.
NOTE: We have this issue since upgrading to Xamarin.Forms 2.0, everything was working fine before
I'm seeing the same described behavior on the version prior to 2.0, as something to take note of.
This is fixed with 220.127.116.1184
18.104.22.16884 fixed the issue in my repro case I sent you. In the real app however, we use an animation to fade the element in. This still is not working correctly.
See the updated version of the project here: https://github.com/philippd/ContentView-Bug.git
The workaround for me is still the same: Setting the ContentView to visible and opacity to zero before changing the content works.
Should I open a new bug for this?
Please do, i will look at it.