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

Cannot distinguish whether App was crashed from Sentry issue details #709

Closed
4 of 7 tasks
whatwg6 opened this issue Oct 30, 2019 · 1 comment
Closed
4 of 7 tasks

Comments

@whatwg6
Copy link

whatwg6 commented Oct 30, 2019

OS:

  • Windows
  • MacOS
  • Linux

Platform:

  • iOS
  • Android

SDK:

  • @sentry/react-native
  • react-native-sentry

react-native version: 0.61.0

Init Code:

import * as Sentry from '@sentry/react-native';

const sentryConfig = {
  dsn: 'https://[email protected]/1783820',
};
global.Sentry = Sentry;
global.Sentry.init(sentryConfig);

I have following issue:

It was excited that when our team using Sentry for Error tracing. Some problems was out, we don't know whether Error was cause App crash.

Description goes here ...

Steps to reproduce:

// Test.js
function Test(props) {
    const {a: {b: c}} = this.props
    return 'test commponent'
}

// App.js
function App() {
     return <Test />
}

Actual result:

  • report err to Sentry
  • App crashed

Expected result:

  • report err to Sentry
  • App crashed
  • sentry issues has crash signature
@whatwg6 whatwg6 changed the title Cannot differentiate whether App was crashed from Sentry issue details Cannot distinguish whether App was crashed from Sentry issue details Oct 30, 2019
@whatwg6
Copy link
Author

whatwg6 commented Dec 4, 2019

for a long time I found that level: fatal will cause App crash,level error may cause white screen。close this issue

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