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 42793 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
On Windows platforms (WinRT 8.1, WinPhone RT 8.1, and UWP), I define DISABLE_XAML_GENERATED_BREAK_ON_UNHANDLED_EXCEPTION in the project properties, and then implement my own UnhandledException handler as follows:
UnhandledException += async (sender, eo) =>
eo.Handled = true;
Exception ex = eo.Exception as Exception;
if (ex != null)
// TODO - attempt to use localised text first, but then fallback to hardcoded text if the localised fails
MessageDialog md = new MessageDialog(
"Something went wrong with the app. Probably best to re-start it as soon as possible.",
catch (Exception ex)
Note that InsightsWrapper is just a thin wrapper around Insights/HockeyApp.
On UWP (both 32 and 64 bit builds), the above code does what I would expect, popping up the MessageDialog and waiting for the user to hit the button on the dialog.
However, on WinRT 8.1 and WinPhone RT 8.1, it seems that setting Handled on the exception object has no effect. Despite setting Handled = true, and doing the await, the application closes rather than waiting for the user to respond (and then carrying on as before).