I just started using React Native Firebase and Crashlytics (version 6). When I call firebase.crashlytics().recordError(error)
in a JS catch
block I see errors similar to the following in the Firebase Crashlytics logs. Is this the expected behavior?
This error log does not have any useful information, so I'm not sure if I'm using it correctly. (I thought about creating this as a bug report, but this seems like either the expected behavior or user error).
Errors triggered:
Stack trace from one of the errors:
If this is the expected behavior, I will probably call it like this: firebase.crashlytics().recordError(new Error('The error description');
. That way I know where the error was, since I won't be able to tell from the line number where the error was. The downside of this is that it won't show the actual error message, so I'd know where the error was, but not what the error was.
Overall React-Native Firebase is working great for me, so thanks for all the hard work (if you're part of the team)!