Closed sujayjaju closed 5 years ago
BTW. the issue is only in dev mode. works in production.
This is because RN catches these in Dev so it can display the RedBox; I'm not sure there's anything that can be done about it afaik but I will look at it as part of v6.0.0, you can track this via: https://github.com/orgs/invertase/projects/2#card-17470855
Loving react-native-firebase
and the support we provide? Please consider supporting us with any of the below:
React Native Firebase
and Invertase
on Twitter Ok, makes sense. I would suggest adding a note about it in the docs. I spend good amount of time trying to figure out why.
Can I clarify here.. so crashes DO NOT, by default get submitted to the dashboard? Unless you do react-native run-ios --configuration Release
?
It took me a long time via trial and error to figure that one out. This should be more clearly stated on Firebase Crashlytics site. Coming from Fabric Crashlytics, you can have crash logging be reported even in debug mode.
Fatal errors not getting caught / reported.
I have crashlytics integrated and connected to firebase console. I can see
firebase.crashlytics().recordError(...)
in the console. Butfirebase.crashlytics().crash()
fails to record. Logcat says "No record found." on restarting the app.The same setup works on iOS
Project Files
iOS
ios/Podfile
:AppDelegate.m
:Android
android/build.gradle
:android/app/build.gradle
:android/settings.gradle
:MainApplication.java
:AndroidManifest.xml
:Environment
ADD_SOMETHING_HERE
e.g. iOS 10 or Android API 28N/A
N/A
N/A
27.0.3
React Native
version:0.55.4
React Native Firebase
library version:5.2.2
Firebase
module(s) you're using that has the issue:TypeScript
?N/A
ExpoKit
?ExpoKit
N/A