#Finding React Native Web crashes

6 messages · Page 1 of 1 (latest)

lavish forge
#

How do I filter the Issues list to only show crashes in the React Native Web version of our app?

atomic jackalBOT
#

Hi @lavish forge. I'm happy to dig into this for you! I'll check my internal sources for answers to your question! :wave:

#

To filter your Issues list to show only crashes in the React Native Web version of your app, you can use Sentry's filtering capabilities. Based on the knowledge sources, there are a couple of approaches you can take:

  1. Filter by OS/Platform: You can filter issues by operating system using the os.name filter in Sentry's Issues view or Discover queries. This would allow you to specifically target web-related issues.

    As mentioned in a Sentry discussion: Visualize errors by OS, Sentry has "the ability to filter per many things, os being one of them."

  2. Use environment tags: If you've set up different environments for your React Native Web version versus your native mobile versions, you can filter by the environment tag.

It's worth noting that React Native Web is not officially supported by the Sentry React Native SDK. There was an issue related to this where ErrorUtils was not defined on the web platform, which was fixed in version 4.14.1. As mentioned in the issue: Issues integrating @sentry/react-native into a project that uses react-native-web, "Note that react-native-web is not officially supported. You will need to add GlobalHandlers and TryCatch to the integrations to get web errors."

If you're using both the React Native SDK and a web-specific SDK, you might need to configure them carefully to avoid conflicts while ensuring you capture all relevant errors.

For more detailed filtering options, you can refer to Sentry's documentation on Issues and Discover queries which provide extensive filtering capabilities.

#

I hope this helps! Let me know if you need more specific guidance on setting up these filters.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@lavish forge Our robots are still learning and improving, please let us know if this response was correct by reacting below.

lavish forge
#

The os.name field does not allow for "web". So your suggestion will not work. <@&1344590412081401867>