Replies: 1 comment
-
I finally found answer in this comment // When we have an unhandled managed exception, we send that to Sentry twice - once managed and once native.
// The managed exception is what a .NET developer would expect, and it is sent by the Sentry.NET SDK
// But we also get a native SIGABRT since it crashed the application, which is sent by the Sentry Cocoa SDK.
// This is partially due to our setting ObjCRuntime.MarshalManagedExceptionMode.UnwindNativeCode above.
// Thankfully, we can see Xamarin's unhandled exception handler on the stack trace, so we can filter them out.
// Here is the function that calls abort(), which we will use as a filter:
// https://github.com/xamarin/xamarin-macios/blob/c55fbdfef95028ba03d0f7a35aebca03bd76f852/runtime/runtime.m#L1114-L1122 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed that the same app version may use different sdks for error reporting.


I have read the source code, but I don't understand anyway why sdk is different. According to SentrySdk.cs, Cocoa SDK should always be used on iOS
Code from SentrySdk.cs:
Beta Was this translation helpful? Give feedback.
All reactions