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

Android ignores "enableNativeCrashHandling" flag #748

Closed
4 tasks
crazyjooe opened this issue Jan 27, 2020 · 1 comment · Fixed by #749
Closed
4 tasks

Android ignores "enableNativeCrashHandling" flag #748

crazyjooe opened this issue Jan 27, 2020 · 1 comment · Fixed by #749

Comments

@crazyjooe
Copy link

OS:

  • Windows
  • [X ] MacOS
  • Linux

Platform:

  • iOS
  • [ X] Android

SDK:

  • [X ] @sentry/react-native
  • react-native-sentry

react-native version: 0.61.2

Init Code:

Sentry.init({
  enableNative: true,
  enableNativeCrashHandling: false,
  enableNativeNagger: false,
  dsn: 'https://...@sentry.io/...'
});

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:

  • 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.
@HazAT
Copy link
Member

HazAT commented Jan 27, 2020

Thanks for reporting, we will check and fix it with this PR: #749

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

Successfully merging a pull request may close this issue.

2 participants