Philipp Hofmann

This would break the SDK crash detection: https://github.com/getsentry/sentry/issues/44342. We want that the SDK sends the crash event. If our SDK keeps crashing, we have the report start-up crashes feature to...

> In the case you describe where we cause an app launch crash and say we should let it happen so customers are aware, I disagree. I might have been...

We'll discuss it in our next sync.

This was fixed with #3699.

If we add an overload for `beforeSend` with a `hint` we can do this without a breaking change.

On Java, we have [typed hints](https://github.com/getsentry/sentry-java/tree/beba01476ab71745b0cae821bed705d582374161/sentry/src/main/java/io/sentry/hints). I think that would be better than having a `Map`.

Hints must allow capturing stacktraces only for one event if capture stacktraces is disabled in the options, as requested in https://github.com/getsentry/sentry-cocoa/issues/3386.

@jozefizso, as pointed out above, this should be fixed with [8.15.0](https://github.com/getsentry/sentry-cocoa/releases/tag/8.15.0).

@armcknight, do you have any ideas on why `SentryTransactionContext getThreadInfo` could crash with an `EXC_BAD_ACCESS`? Once crash points to `sentry::profiling::ThreadHandle::current()`.

If I got it right, all you need is `SentryBaggage`, `SentryTraceContext` and `SentryTraceContext.toBaggage` being public, @kabiroberai? [Baggage](https://github.com/getsentry/sentry-java/blob/937879e7bffe6eceeb2ed339971da869fd0df542/sentry/src/main/java/io/sentry/Baggage.java#L27) and [TraceContext](https://github.com/getsentry/sentry-java/blob/937879e7bffe6eceeb2ed339971da869fd0df542/sentry/src/main/java/io/sentry/TraceContext.java#L14) are also public on Java. @brustolin, can you think of any...