Philipp Hofmann

Maybe merging some of the latest changes from [KSCrashMonitor_MachException](https://github.com/kstenerud/KSCrash/commits/master/Source/KSCrash/Recording/Monitors/KSCrashMonitor_MachException.c) to SentryCrashMonitor_MachException could solve the issue. The same applies for [KSCrashMonitor_CPPException](https://github.com/kstenerud/KSCrash/blob/master/Source/KSCrash/Recording/Monitors/KSCrashMonitor_CPPException.cpp)

Maybe related to - https://github.com/getsentry/sentry-cocoa/issues/1562 - https://github.com/getsentry/sentry-cocoa/issues/1533 - https://github.com/getsentry/sentry-cocoa/issues/1589

@armcknight, please add the `Type: Flaky Test` label the next time so we can easily keep track of the flaky test issues.

@brustolin, can you think of any other features that need testing? If so, please add them above.

I finished testing; see above.

App hangs is already GA but disabled per default. I opened a PR to update the wizard https://github.com/getsentry/sentry-docs/pull/5517 and to mention experimental features in getting started https://github.com/getsentry/sentry-docs/pull/5518.

I think we could enable core data and file I/O per default also in a minor release once we know it doesn't break anyone. Those features only add spans, so...

All done expect user interaction tracing. Created an extra item for this https://github.com/getsentry/sentry-cocoa/issues/2298

This only makes sense if we can map the absolute time back to NSDate. Consider updating the develop docs to use wall time for tracing. A maybe useful resource https://linux.die.net/man/3/clock_gettime

> > Yeah I actually wanted to ask about that - what is the use of that initWithDict method anyways? Who's using this, and why? > > I believe this...