Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we use the log function in Crashlytics.js #219

Open
benjarwar opened this issue May 1, 2019 · 1 comment
Open

Can we use the log function in Crashlytics.js #219

benjarwar opened this issue May 1, 2019 · 1 comment

Comments

@benjarwar
Copy link

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.

@benjarwar
Copy link
Author

benjarwar commented May 1, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant