Skip to content

Unhandled Microsoft.UI.Xaml.Application.Current.UnhandledException should also fire AppDomain.CurrentDomain.UnhandledExceptionΒ #10560

Open

Description

Describe the bug

It's really nice to have a chance to connect to Microsoft.UI.Xaml.Application.Current.UnhandledException and sometimes recover from it (Handled = true). But when that property isn't touched, I feel like the AppDomain.CurrentDomain.UnhandledException should fire as well.

It allows for a single collection point for crash reporting platforms...

Steps to reproduce the bug

/

Expected behavior

UI thread exceptions also firing AppDomain.CurrentDomain.UnhandledException id Handled isn't set to true

Screenshots

No response

NuGet package version

None

Windows version

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Crashwhenever user reports a crash or app freezearea-C#/WinRTbugSomething isn't workingteam-CoreParent label for issues owned by the Reach, Rendering, or Markup teams

    Type

    No type

    Projects

    • Status
      Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions