Skip to content

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

@bialasik

Description

@bialasik

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://...@sentry.io/...', {
   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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions