-
-
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
Broken Grouping of crash events cause no thread has crashed true #4578
Comments
yes, We want to group based on stack trace as well. There is another instance for different stack traces: Sentry Group link: https://citrix-workspace.sentry.io/issues/5889315885/events/ff75ad4fc2234f1287833923c2d6cb[…]lved&referrer=next-event&statsPeriod=30d&stream_index=1 1 event id: ff75ad4fc2234f1287833923c2d6cbc1 |
I found the reason why Sentry doesn't group it by stacktrace: |
Platform
macOS
Environment
Production
Installed
Swift Package Manager
Version
8.36
Xcode Version
15.4
Did it work on previous versions?
No response
Steps to Reproduce
No steps to repro, Issue happens randomly
Expected Result
All crash events groups should have similar report.
Actual Result
For the below group we have different stack traces for different events:
https://citrix-workspace.sentry.io/issues/5782612431/events/98609bd2abc448bc8b236e992924f953/?project=4507448592105472&query=error.unhandled%3Atrue%20is%3Aunresolved&referrer=next-event&sort=freq&statsPeriod=14d&stream_index=1
stack trace: 39a6d7eaff9040e2bee50fea7fa444a4
stack trace: 98609bd2abc448bc8b236e992924f953
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: