How to trace exact issue from Firebase Crashlytics log in React Native App?

Viewed 421

I have a React Native app with Firebase crashlytics integrated. I am forcefully crashing the app by calling function which does not exist. (this.test()).

I am getting logs in crashlytics, but looking at that logs I am not able to track the exact issue location. Logs are quite generic and which is not helping me to pinpoint the issue.

Is there any way to get more info on that issue from logs? or anything I need to do so that I can get the issue location? if we are getting an issue in the inded.js file can we trace back the exact js file in app which is causing the issue.

Please help me with this information. Than you for helping.

1 Answers

Firebaser here - it sounds like you'd benefit from Crashlytics custom logging. This tool allows you to log any messages you want that get appended to the Crashlytics crash report that gets sent up to the console. I'm not sure how the React Native wrapper for Firebase Crashlytics works or if it allows you to do this, but according to the React Native Firebase reference doc you should be able to.

With this tool, you could call log in your code whenever you want to record information about the session, the user, or whatever's happening with code that you're executing in the background.

Related