Prevent potential SHA-1 hash mismatch in Bugsnag-Integrity header for session requests #1043
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.
Goal
Prevents a SHA-1 hash mismatch when the React Native notifier changes the
notifier
field on startup. Because the Android notifier assigns the event payload value by reference fromClient#notifier
, the request payload can change between generating a SHA-1 hash and making the request.Changeset
Copied the
notifier
parameter when constructing aSession
, so that it does not hold a copy of global state.Testing
Added unit test to verify that the
notifier
property is always copied when constructing aSession
.