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.
Created attachment 14558 [details]
Our app currently crashes when I quickly add/remove Image views. I have a search function implemented which shows search results with images, however when the user quickly changes the search query and presses the search button again (thus reloading the results and their images) the app crashes with a NullReferenceException:
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
I have attached a test project which replaces a single Image view every 50ms to force the crash.
I am also facing the exact same issue when when changing the images.
Me too, exactly same call stack, any known workaround for this?
Should be fixed in 2.2.0-pre1
I'm facing the same issue not only when I quickly change images but also when I get for the 1st time on the view where the image should be displayed.
Is there a way to catch this exception ? Or any workaround ?
I have to deliver an app soon and it's a problem.
I'm facing the same issue in both UWP and WindowsPhone 8.1. It majorly happens in Windows Phone 8.1 project. Is this fixed for WindowsPhone 8.1 as well?
I have checked this issue with Xamarin.Forms 220.127.116.11-pre2 and observed that its working fine.
Hence closing this issue.
@Samih, @Harikrishnan, If you getting other issue please filed a separate bug for the same.