reportCrash shows up in Sentry #2648
Replies: 2 comments
-
Hi @janwiebe-jump. I moved this to a discussion as it's not directly an issue related with Ignite but you seem to have some questions about best practices around Sentry. Could you give us some more info so we can help you? What version of Ignite/Expo/Sentry are you using. Perhaps the package json and where your try/catch is where you are reporting the error? You can also enhance the reporting feature to include level, etc. See the docs here: https://docs.sentry.io/platforms/react-native/usage/set-level/ |
Beta Was this translation helpful? Give feedback.
-
I changed the issue grouping in my Sentry project settings, by adding a line for the Based on this documentation |
Beta Was this translation helpful? Give feedback.
-
When calling reportCrash from within my code, to log the error to Sentry, it always shows up as 'reportError'.
The actual error is somewhat hidden in the subtitle.
Any ideas to make this a more useful display? For example the source where the reportCrash was called?
Beta Was this translation helpful? Give feedback.
All reactions