It would be good to have the same behaviour in Crashlytics.
The changelog URL for v6 is here now https://github.com/invertase/react-native-firebase/blob/master/CHANGELOG.md#crashlytics-crashlytics
@Mike Diarmid so is there any way to sourcemap the stacktrace? how can we store it externally and how can we decode the stacktraces?
Implemented in v6, see https://github.com/invertase/react-native-firebase/blob/master/CHANGELOG.md#crashlytics
Hey all, this is in progress now for v6; JS errors will be captured; however there's still no way to include a source map except storing it externally (we'll add some docs for this though).
You can track the progress here: https://github.com/orgs/invertase/projects/2#card-17470855 & https://github.com/invertase/react-native-firebase/tree/master/packages/crashlytics
@Mike Diarmid: May I know is there a way to provide sourcemap to RNFB? If so, where is it documented. Sorry can't seem to find it
@Mike Diarmid: agreed, source maps would be a great feature. We are currently using crashlytics at the company I'm working for and this would really improve our implementation.
Something related to source map.