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 36600 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 14128 [details]
On Android, changing an Image.Source at runtime causes an undesired visual "flickering".
**Steps to Reproduce:**
1. Run the attached on an Android emulator
2. Press the Test button repeatedly
The "Label Test Test" should not jump to the top and back to the bottom when the image changes. Similar to how the iOS project works (run that on the iOS simulator to see).
**Build Date & Platform:**
Note that a similar sounding bug has been raised against Windows and WinPhone 8.1, number 37237. I suspect it has a different cause, but mention it here just in case.
Created attachment 15067 [details]
Sample using Java demonstrating a lack of flicker
It appears that setting the height and width for the image explicitly removes the flicker.
This can be done via the HeightRequest and WidthRequest properties, such as:
>image.HeightRequest = 234;
>image.WidthRequest = 234;
Created attachment 15068 [details]
Xamarin.Android Project(Does not demonstrate behavior)
Customer just indicated he has set width and heightrequest but still has issues with flicker.
I wanted to chime in and confirm I am also experiencing the issue in Xamarin.Forms 18.104.22.168. It is quite ugly and I have to imagine fairly common, anyone who has a data binding on an ImageSourceProperty must be experiencing it. Is there anything in the works to ameliorate the problem, or any workarounds? (Such as overriding an event in a custom renderer or something)
Jordan - as a workaround (although not a nice one), if you know what images can appear at a particular position, rather than use ImageSource to replace one by another, actually overlay multiple images of the same size at the same location, and use IsVisible and/or Opacity to make just one visible at any time.
I use this technique for producing buttons with multiple states (e.g. expander/contractor buttons, checkboxes etc), as well as using this same technique to implement a generic ContentButton and a decent ImageButton.
Be aware though, that this technique currently shows up a couple of other bugs on WinRT and UWP, with a particularly nasty one where this technique is used in a Grid in a ViewCell in a ListView. Also, if combining with a button at the same location, you might need to use an opacity around 0.02 rather than use IsVisible to hide the button.