-
-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WinUI doesn't report all crashes #3795
Comments
Assigning to @getsentry/support for routing ⏲️ |
A repro would be helpful. But we can try to poke at artificial way to cause those errors. I suspect that these are native crashes and we don't capture them. sentry-native is enabled if compiling with Native AOT then all native crashes are captured but not sure how WinUI gets deployed, if it's already available for Native AOT or it's still .NET Native. Or something else. @jamescrosswell for thoughts |
We currently only include sentry native on android, ios and maccatalyst targets: sentry-dotnet/src/Sentry/Sentry.csproj Lines 24 to 25 in ecc5812
It might be possible to include this for WinUI applications as well... providing the WinUI apps in question target net8.0 or later (so something like |
Environment
SaaS (https://sentry.io/)
What are you trying to accomplish?
(Org recently transitioned their WinUI app from using AppCenter)
Certain crashes are not appearing in Sentry.
System.Runtime.InteropServices.COMException (e.g. "The application called an interface that was marshalled for a different thread" with error code 0x8001010E) and AccessViolationExceptions aren’t being logged in Sentry.
Crashes are recorded in AppCenter after the app restarted, but do not appear in Sentry. Why aren't these types of exceptions being captured?
How are you getting stuck?
They could not reproduce, but gave permission to post their configs here:
NLog CONFIGURATION:
SENTRY CONFIGURATION:
Where in the product are you?
Issues
Link
No response
DSN
No response
Version
No response
┆Issue is synchronized with this Jira Improvement by Unito
The text was updated successfully, but these errors were encountered: