Open benjarwar opened 5 years ago
Similarly, can we use recordCustomExceptionName
to log fatal and/or non-fatal exceptions? It seems to provide an API for passing a custom error name and stack, whereas logException
(for Android only) and recordError
(for iOS only) end up all grouped together under the same error, such as com.smixx.fabric.SMXCrashlytics.logException
for Android. This makes it challenging to sort different JS errors according to their underlying causes.
This isn't listed in the Crashlytics usage, but I noticed there's a
log
function in Crashlytics.js. Can we use that to push logs (for either/both Android/iOS) for subsequent Crashlytics errors?Currently, we're implementing custom native solutions for persisting logs, but it'd be preferable to use
react-native-fabric
for since we're already using it for error handling.