Philipp Hofmann
Philipp Hofmann
@kode54, to your unrelated topic: This looks like a completely different problem. Please open an extra issue for this.
@kode54, we closed the other is as not planned, because we will fix the underlying problem with https://github.com/getsentry/sentry-cocoa/issues/4950.
@kode54, when the underlying issue is something different, I think we should close this issue and open a new one referencing this one.
Thanks for reporting this, @demonukg. After a quick glance I have no clue what could cause this. We need to investigate.
I fixed point 5 with https://github.com/getsentry/sentry-cocoa/pull/4028.
Thanks for double-checking, @adinauer 😃 . Crashes are out of scope for this issue. We are going to tackle these after merging https://github.com/getsentry/sentry-docs/pull/15274.
@philprime, yes, I plan to next week. I mean, you or anybody else can also pick it up if you have bandwidth.
I manually tested capturing a message with the iOS-Swift sample app ```swift let message = Data(repeating: 0, count: 1024*1024*2) // 2 MB message let string = message.base64EncodedString() let eventId =...
Back to draft because some tests are failing.
We see a couple of fatal app hangs in our internal [SDK crash detection](https://sentry.sentry.io/issues/6816688350/?project=4505469596663808&query=is%3Aunresolved%20fatal%20app&referrer=issue-stream) with the stack trace pointing to this root cause ``` Thread 0 Crashed: 0 libsystem_kernel.dylib 0x1e2ad20c8...