Does bugsnag-expo capture native errors when used with expo-dev-client and EAS builds?

[evelant]

Per the title, is bugsnag-expo configured to compile full react-native support with expo-dev-client to capture native android/ios errors? Or is it a JS only package at this point?

[luke-belton]

Hi @evelant - currently bugsnag-expo only works with the JavaScript part of Expo apps. We have an item on our roadmap to look at full native support in the future, however I don't currently have an ETA for that work. I'll make sure we keep this thread updated when there are any changes.

[smn-snkl]

@luke-belton would you recommend switching to bugsnag for react-native instead of the expo package then? Seems like the expo version has some significant drawbacks.

[enagorny]

Using bugsnag react-native isn't possible in managed workflow. And I think you don't want to eject it.
The solution might be to create expo-config-plugin which will do following steps https://docs.bugsnag.com/platforms/react-native/react-native/manual-setup/ from the config plugin.

All of the above should be done on the react-native-bugsnag and not here.

https://docs.expo.dev/develop/development-builds/introduction/
https://docs.expo.dev/modules/config-plugin-and-native-module-tutorial/

@bugsnag/react-native-cli is already doing something similar manually
https://github.com/bugsnag/bugsnag-js/tree/next/packages/react-native-cli
but for the expo it need to rewritten as expo config plugin

@luke-belton please let me know if you need any help with it

[johnkiely1]

Thanks for the kind offer @enagorny. I've noted this internally with our product team.

More generally the work to support native errors is still on our backlog and we will update here when we have more info to share regarding the timeline and implementation of this.