Replies: 2 comments
-
Hmm from testing as well as this part of the doc: Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform. I'm curious why we call the |
Beta Was this translation helpful? Give feedback.
-
Next.js wraps your entire app in an error boundary, preventing React render errors from bubbling up to the global error handler which we would normally attach ourselves to. This is why we need a specific For all other errors (e.g. ones that are thrown inside event handlers like |
Beta Was this translation helpful? Give feedback.
-
I have a NextJS app. I understand that by adding the captureUnderscoreException call within the custom error page (also known as "_error.tsx", I can capture errors from within the render context.
I'm curious what exactly happens to unhandled errors thrown outside the render context, for example within an
onSubmit
method. Are they automatically logged to Sentry nonetheless? If not, what happens if I have a Sentry transaction started?Beta Was this translation helpful? Give feedback.
All reactions