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

No crash data sent on 'real' error (not throw new Error) #549

Closed
2 of 5 tasks
bialasik opened this issue Feb 15, 2019 · 2 comments
Closed
2 of 5 tasks

No crash data sent on 'real' error (not throw new Error) #549

bialasik opened this issue Feb 15, 2019 · 2 comments

Comments

@bialasik
Copy link

bialasik commented Feb 15, 2019

OS:

  • Windows
  • MacOS
  • Linux

Platform:

  • iOS
  • Android

Output of node -v && npm -v && npm ls --prod --depth=0

v8.11.4
5.6.0

Config:

Sentry.config('https://[email protected]/...', {
   logLevel: __DEV__ ? SentryLog.Debug : SentryLog.None,
}).install()

Hello. The app doesn't send a crash event from client when it's real crash (not the throw new Error one). It does send errors triggered manually (by throw new Error). Tested on iOS simulator in development mode.

Steps to reproduce:

  • create some faulty code in the app, but able to build, like someObject.nonExistingField.nonExistingField

Actual result:

  • I have an error and red screen on Simulator "TypeError: undefined is not an object (evaluating someObject.nonExistingField.nonExistingField) but there's no error reported to Sentry.

Expected result:

  • error is reported to Sentry and I can see it on the dashboard
@WatsonFungHK
Copy link

did you try Sentry.nativeCrash() ? what is the result

@HazAT
Copy link
Member

HazAT commented Sep 4, 2019

I am closing all old issues, please if this is still a problem feel free to revive it.
Also, consider moving to our new SDK @sentry/react-native if it still happens there please open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants