Dhiogo Brustolin
Dhiogo Brustolin
>I think all sentry targets should have ExceptionProcessor. > >So can both override/replace/reject the exception and send extra data to the exception for its scope. You can use `beforeSend` callback...
More information shared at https://discord.com/channels/621778831602221064/1263605605051142204/1263605605051142204
Thanks for the update @rodolfoBee. We still dont have a solution for this.
Hello @lsnunn, thanks for reaching out. Can you replicate this, or are you simply encountering it randomly in your crash reports?
Ok, this is for the widget then? Good to know. And only in the widget does this error occurs?
Thanks for all the information! We'll investigate this.
Hello @falk-stefan Thanks for reaching out. We will investigate the impact on performance. Were you testing this on debug alone, or did you try a release build? > I removed...
> Essentially, I just commented out the entire section in order to remove the integration like so Ok, so you disabled session replay completely. Thanks for the answers!
> @brustolin Do you also get the Xcode warning? This is supposed to be fixed. I will take a look.
I could reproduce this in an older version, but since Sentry metrics is now dead, this is no longer an issue.