fix: Linking ongoing trace to crash event #4393
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📜 Description
Fix linking a crash event to an ongoing trace by skipping setting the trace context in Scope.applyToEvent for crash events.
💡 Motivation and Context
Fixes GH-4375
💚 How did you test it?
I could reproduce the problem in the SwiftUI sample app with the following code in the SwiftUIApp.swift file:
Event in Sentry before the fix:
Event in Sentry after the fix:
📝 Checklist
You have to check all boxes before merging:
sendDefaultPII
is enabled.🔮 Next steps