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
Then cause the application to crash, and let the plugin catch and report the exception on its own (rather than try/catching and manually reporting it using Sentry.captureException(error)).
The exception will get reported to Sentry, but the JS stack trace will appear as a plain text string and source mapping will not occur. If instead you manually catch and report the exception source mapping will work. Presumably, stack trace frame rewriting only occurs when exceptions are manually caught and reported. This is problematic because you don't know in advance where exceptions will occur, and wrapping all code in try/catch blocks is unfeasible.
The text was updated successfully, but these errors were encountered:
kajic
changed the title
Exceptions must be explicitly caught and reported for stack trace frame rewriting to occur
Exceptions must be explicitly caught and reported for source mapping to work
Jan 24, 2021
Which platform(s) does your issue occur on?
Please, provide the following version numbers that your issue occurs with:
Please, tell us how to recreate the issue in as much detail as possible.
Initialize the plugin like so:
Then cause the application to crash, and let the plugin catch and report the exception on its own (rather than try/catching and manually reporting it using
Sentry.captureException(error)
).The exception will get reported to Sentry, but the JS stack trace will appear as a plain text string and source mapping will not occur. If instead you manually catch and report the exception source mapping will work. Presumably, stack trace frame rewriting only occurs when exceptions are manually caught and reported. This is problematic because you don't know in advance where exceptions will occur, and wrapping all code in try/catch blocks is unfeasible.
The text was updated successfully, but these errors were encountered: