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
The above demo is a vanilla NextJS installation with Sentry installed. The only custom code added is the button that causes an intentional TypeError in the frontend.
The text was updated successfully, but these errors were encountered:
Hey, thanks for reporting and for the detailed repro demo, it's highly appreciated.
The second error is not reported to Sentry because it occurs in the React component tree, so it doesn't bubble up to the global error handlers that Sentry is listening on. Instead, NextJS handles the error (through it's own React Error Boundary), and renders the built in Error component from next/error.
We are working on a) improving our documentation around this and b) seeing if we can get better behaviour out of the box without you having to add an error boundary or configuring pages/_errors.js, will update this issue once we've made progress on that.
Package + Version
@sentry/nextjs
Version:
Description
When an error causes a crash in NextJS, it is not reported to Sentry, even though the error is logged in the Chrome/browser console.
Reproducable Demo can be found here: https://github.com/zacharypodbela/sentry-nextjs-crash-demo
The text was updated successfully, but these errors were encountered: