You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally, I found that the bugsnag-cocoa pod also hard-codes attachment of stack traces to the first error in the BugsnagEvent#errors array in the attachCustomStacktrace function which is also called in the event deserializer here (this makes it difficult to provide a full solution without also making changes to bugsnag-cocoa or duplicating some logic from bugsnag-cocoa into the bugsnag-js repo).
Describe the bug
package:
@bugsnag/react-native
iOS does not report error causes (It works fine in Android).
Root cause is that the iOS event deserializer is hard-coded to only inspect/deserialize the first error that is reported
bugsnag-js/packages/react-native/ios/BugsnagReactNative/BugsnagEventDeserializer.m
Line 48 in 05588a1
Additionally, I found that the
bugsnag-cocoa
pod also hard-codes attachment of stack traces to the first error in theBugsnagEvent#errors
array in the attachCustomStacktrace function which is also called in the event deserializer here (this makes it difficult to provide a full solution without also making changes tobugsnag-cocoa
or duplicating some logic frombugsnag-cocoa
into thebugsnag-js
repo).Steps to reproduce
Environment
7.20.2
Example code snippet
The text was updated successfully, but these errors were encountered: