Philipp Hofmann
Philipp Hofmann
I'm closing this because, as mentioned here: https://github.com/getsentry/sentry-cocoa/pull/3896#issuecomment-2078810659, we will add hints at some point.
@RadagastCH, are you 100% sure this error is related to the sentry-cocoa SDK? Does the error disappear when you roll back to `8.21.0`? When looking at suggestions to solve this...
@RadagastCH, again looking at this issue, I guess that it has something to do with > macOS app with extensions that used Sentry What exactly do you mean by that?...
> Interestingly enough - even after removing the framework everything works properly, so the framework that is being copied is just a few KB. It looks like a side effect...
@grzegorzkrukowski, as this changed from Xcode versions, why do you think it's a problem caused by the Sentry SDK? Do you see any problems with Sentry at runtime for universal...
Thanks for the update, @grzegorzkrukowski, and for answering all my questions. Now it makes sense to me. We have to investigate this.
I follow the KSCrash repo and apply patches if I see anything useful. A year ago or so, I once skimmed through all the patches and applied the useful ones...
I think we can close this, as we have all the patches applied from there. See https://github.com/getsentry/sentry-cocoa/issues/3900#issuecomment-2077240167.
@sebj, I can reproduce the problem. Using `Sentry-Dynamic` via SPM works, though. Maybe you can switch to that while we are working on a fix.
Thanks for the input, @rhcarvalho. I am also in favor of (3), but I don't fully understand why the con is a con?