chore: Adds SentryFileManager and SentrySerialization to dangerous files #4307
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
💡 Motivation and Context
Adds SentryFileManager and SentrySerialization to list of dangerous files. A recent (GH-4219) change in these files is the likely root cause of invalid envelopes that subsequently caused crashes.
#skip-changelog
💚 How did you test it?
n/a
📝 Checklist
You have to check all boxes before merging:
I added tests to verify the changes.sendDefaultPII
is enabled.I updated the docs if needed.Review from the native team if needed.🔮 Next steps