Fix unrecognized selector crash when adding metadata #429
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 an unrecognized selector crash when adding metadata to a report in a beforeSend block.
The root cause of this bug is that an
NSDictionary
can be a tab value in the metadata property, whereas we assume that this is always anNSMutableDictionary
. Adding a new attribute therefore triggers a crash, because bugsnag-cocoa attempts to mutate an immutable dictionary here: https://github.com/bugsnag/bugsnag-cocoa/blob/master/Source/BugsnagCrashReport.m#L396Setting a user then starting a session provides one way to manifest this bug, as this uses an
NSDictionary
rather thanNSMutableDictionary
when deserializing crash reports. If an attribute is then added to an existing tab (e.g. app, device, user) in a beforeSend callback, this will crash the app: https://github.com/bugsnag/bugsnag-cocoa/blob/master/Source/BugsnagCrashReport.m#L259Changeset
Converted the tab value to an
NSMutableDictionary
if it was not already of this type.Tests
Manually verified that a report is now sent to the dashboard with the example case.