You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to use Sentry to report only React Native crashes, as we are already using another tool for Native ones, and we want to keep them separated.
enableNativeCrashHandling key is the one that should control this behavior. It's handled properly in iOS (can be checked by search, but it seems that it's not handled at all on Android side. After integrating Sentry and making the first release, we started getting Android crash reports as well. This seems like a pretty critical bug at this point, so we have to disable Android integration until it's fixed.
Description goes here ...
Steps to reproduce:
Integrate Sentry and set enableNative to true and enableNativeCrashHandling to false. Get Android to crash on native side.
Actual result:
Android native crash is reported to Sentry, even though it's configured to not handle native crashes.
Expected result:
Native crashes are not reported.
The text was updated successfully, but these errors were encountered:
OS:
Platform:
SDK:
@sentry/react-native
react-native-sentry
react-native
version: 0.61.2Init Code:
I have following issue:
We want to use Sentry to report only React Native crashes, as we are already using another tool for Native ones, and we want to keep them separated.
enableNativeCrashHandling
key is the one that should control this behavior. It's handled properly in iOS (can be checked by search, but it seems that it's not handled at all on Android side. After integrating Sentry and making the first release, we started getting Android crash reports as well. This seems like a pretty critical bug at this point, so we have to disable Android integration until it's fixed.Description goes here ...
Steps to reproduce:
enableNative
totrue
andenableNativeCrashHandling
tofalse
. Get Android to crash on native side.Actual result:
Expected result:
The text was updated successfully, but these errors were encountered: