Seeing unhandled SIGABRT xamarin_unhandled_exception_handler crashes on MAUI iOS

[MichaelLHerman]

Package

Sentry

.NET Flavor

.NET

.NET Version

8.0

OS

iOS

SDK Version

4.10.1

Self-Hosted Sentry Version

No response

Steps to Reproduce

Unsure of how to reproduce

https://cricket-health-ml.sentry.io/issues/5858865093/events/?cursor=0%3A50%3A0&environment=production&project=4507788345868288&referrer=issue-stream&statsPeriod=14d&stream_index=3

Seeing a bunch of SIGABRT xamarin_unhandled_exception_handler (Signal 6, Code 0) unhandled crashes.
From looking at Sentry code, it appears these are supposed to be filtered out client side but I don't see corresponding managed crashes being reported (when I search by app.device or user.username tags, I don't see other managed crashes) so I have no way to look into the underlying cause.

Expected Result

Should see managed crashes, and not these native crashes

Actual Result

See plenty of instances of SIGABRT xamarin_unhandled_exception_handler (Signal 6, Code 0) with no corresponding managed crash

[jamescrosswell]

From looking at Sentry code, it appears these are supposed to be filtered out client side but I don't see corresponding managed crashes being reported

Hey @MichaelLHerman, reading Matt's comment in that Sentry snippet you referenced:

When we have an unhandled managed exception...

Since you're not seeing any managed exceptions, my assumption would be that this SIGABRT is coming from unmanaged (not managed) code. What does the full stack trace look like (rather than just the "Most relevant" - which seems to be showing just In App frames)?

[MichaelLHerman]

@jamescrosswell

The only frames that are omitted by "Most relevant" are pthread_kill and abort. Since the frames below it are mono/xamarin I assume this is a managed exception.

Thread 0 name: tid_103 Crashed:
0   libsystem_kernel.dylib          0x3b9ee42ec         __pthread_kill
1   libsystem_pthread.dylib         0x3e1acfc08         pthread_kill
2   libsystem_c.dylib               0x338479b9c         abort
3   CadabraMobile                   0x205241d20         xamarin_unhandled_exception_handler (runtime.m:1133)
4   CadabraMobile                   0x2054459dc         mono_invoke_unhandled_exception_hook (exception.c:1219)
5   CadabraMobile                   0x2054e0408         [inlined] mono_jit_exec_internal (driver.c:1374)
6   CadabraMobile                   0x2054e0408         mono_jit_exec (driver.c:1314)
7   CadabraMobile                   0x20524a2f0         xamarin_main (monotouch-main.m:495)
8   CadabraMobile                   0x205548ef4         main (main.arm64.mm:376)
9   <unknown>                       0x1c3b63154         <redacted>

[jamescrosswell]

@MichaelLHerman I agree. I don't have any theories as to why this might be happening though. If we could reproduce the problem, it would be possible to look into it further.