[PLAT-8219] Fix crash when using BugsnagNetworkRequestPlugin alongside New Relic #1324
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
Fix a crash that occurs when
BugsnagNetworkRequestPlugin
is linked into a project that uses the New Relic.Sample crash:
Changeset
Uses the lighter-weight forwardingTargetForSelector: mechanism instead of implementing methodSignatureForSelector: and forwardInvocation:.
It's not entirely clear why this fixes the crash, but it does in the example app used, and is also faster 🚀
New Relic's session delegate implements
forwardingTargetForSelector:
rather thanforwardInvocation:
and the crash presumably arose because of the mismatch.Testing
Reproduced the crash by creating an example app that uses BugsnagNetworkRequestPlugin, New Relic, and initiates a download task using Moya.