Matt Johnson-Pint

Ok, researching more, this was helpful (both "Default log level" and "Filter function" right below it). https://learn.microsoft.com/en-us/dotnet/core/extensions/logging#default-log-level Thus, instead of `SetMinimumLevel`, we can use: ``` builder.AddFilter(_ => true); ``` That...

Changing my mind about this - it certainly is a bug, not an enhancement. The intent was always that `MinimumEventLevel` and `MinimumBreadcrumbLevel` could be set independently of any other logging...

Some previous discussion on this here: https://github.com/getsentry/develop/issues/443 Also relates to #1844

My inclination is to do two things: 1. In [`Hub.CaptureEvent`](https://github.com/getsentry/sentry-dotnet/blob/19da8b8885e4b98b650714754b919d758df0784b/src/Sentry/Internal/Hub.cs#L303-L344) we already have some logic for marking sessions as crashed for unhandled exceptions. We could also finish open transactions there...

For now, let's forgo the API change and just focus on closing the transaction with an error status (See 1 above).

Probably should return `Aborted` as a status? https://github.com/getsentry/sentry-dotnet/blob/19da8b8885e4b98b650714754b919d758df0784b/src/Sentry/SpanStatus.cs#L56

https://docs.sentry.io/product/profiling/

Looks like we are applying this in `MainSentryEventProcessor` https://github.com/getsentry/sentry-dotnet/blob/7e455257ad1fcd708be847cf2b416a10e7488b0b/src/Sentry/Internal/MainSentryEventProcessor.cs#L75-L86 We may want to add a main transaction processor to cover this. Perhaps there are other things to apply by default...

Thanks for reporting. I'll investigate.

Hi, a few questions: - Is this a physical device, or a simulator? - What version of iOS is it using? - Does it *only* happen with hot reload? Or...