-
-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception parsing seems a bit off #3707
Comments
I'm still seeing this. I'm getting this crash in multiple apps and unable to fix it as the crash report is not actionable... Another report: https://sindresorhus.sentry.io/share/issue/ab8eb435cc71469082a07cdbece72d70/ |
@sindresorhus Thank you for the new link. |
I finally had a user send me a local crash report for this, and comparing it to the Sentry raw crash report, it seems like Sentry is truncating the Sentry
Local crash report
|
@sindresorhus Thank you for all the extra data this will make it much easier to debug. |
Any updates? This is still a huge issue. Another report: https://sindresorhus.sentry.io/share/issue/ab8eb435cc71469082a07cdbece72d70/ |
Sadly, no update yet, @sindresorhus. I will talk to the team to raise the priority for this, but I can't give you an ETA yet. |
It looks like the exception parsing is a bit off as some exceptions are reported as:
Notice the
d
.https://sindresorhus.sentry.io/issues/4525409382/events/2a1e0afd32de47d79b68b1b8f2714437/?project=6276511&referrer=previous-event
Originally posted by @sindresorhus in #3265 (comment)
The text was updated successfully, but these errors were encountered: