Native crash reporting for Expo deployed to Android?

user_3781199 0
Viewed 586

I have released an Expo app and now need to remotely deduce the cause of errors. I've exported both an Android and iOS build from Expo with expo build:ios or :android and have deployed them to users via Google play console and iTunes Connect.

A user reported a crash on Android, but in my Google Play console I see no evidence of a crash under "Vitals." This is probably because the app is bundled under the many layers of expo.

I need a way of seeing this crash, so Ive looked at Bugsnag, Sentry and others, but I don't understand whether they will work for this use case.

Will these crash analytics tools give me info if I'm deploying a compiled Android build? Or is this a pre-compile solution?

crashlytics-android expo react-native crash android
1 Answers

One of the projects I worked with uses a combination of React Native and Expo to create Android and iOS versions of the app. The app is released in Google Play and Apple's App Store.

We experienced similar limitations with the crash reporting in Android Vitals and use Sentry for the error reporting. The crashes appear as errors in Sentry. They include additional information such as network requests and responses which can help debug some of the errors.

AFAIK Sentry still offer a free tier that a single developer can use. They and others offer paid-for services. One to consider is RayGun https://raygun.com/blog/react-native-monitoring/ (I've not tried it however the documentation looks like it may suit your needs).

PS: I just discovered that Expo endorse using Sentry https://docs.expo.dev/guides/using-sentry/ which is an encouraging indication Sentry should be suitable.

user_3401750
Related