Example for logging from native side about bugsnag-react-native

[foxyblocks]

For clarification, are you wanting to send two events for the same unhanded exception? Or is is that you want to be able to manually notify bugsnag from the JS side and the native side during different scenarios?

[ptomasroos]

No rather. I have I case I can only detect in my native modules which will never be reachable from js. And it would be very valuable if I could error this from native code. Tomas

…

On 7 Feb 2017, at 17:12, Christian Schlensker ***@***.***> wrote: For clarification, are you wanting to send two events for the same unhanded exception? Or is is that you want to be able to manually notify bugsnag from the JS side and the native side during different scenarios? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ptomasroos]

Last statement is correct.

…

On 7 Feb 2017, at 17:12, Christian Schlensker ***@***.***> wrote: For clarification, are you wanting to send two events for the same unhanded exception? Or is is that you want to be able to manually notify bugsnag from the JS side and the native side during different scenarios? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[foxyblocks]

The react native notifier uses the iOS and Android notifiers to do the actual reporting. You should be able to import and use them directly in native code to report custom or handled exceptions

You should not need to initialize them. By that I mean don't call [Bugsnag startBugsnagWithApiKey:@"your-api-key-goes-here"]; in iOS or Bugsnag.init(this); in Android. The react native notifier will handle the initialization and configuration of the underlying platform notifier.

[kattrali]

I updated the React Native guide to include links to the native interface documentation for reporting handled exceptions, identifying users, and logging breadcrumbs. It should be deployed shortly.