Add unhandled_events field to native payload #445
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.
Goal
ANR detection delivered in #442 means that the number of unhandled events is no longer necessarily 1 in the latest version of the plugin. This requires a migration of existing payloads to fit the new struct, which adds an explicit
unhandled_events
field, rather than hardcoding 1.Changeset
NOTIFY_UNHANDLED
message to the native bridge, which is invoked whenever an unhandled event occurs, and ultimately incrementsreport->unhandled_events
unhandled_events
field tobugsnag_report
, which is serialised rather than '1'bugsnag_report_v1
bugsnag_report_v1
, then copy the fields over tobugsnag_report
.Tests