Open seeARMS opened 2 days ago
Hi, this is a limitation imposed by Next.js.
In theory, you should see the corresponding server error in the trace attached to the error event. That does not seem to be the case. Unfortunately we cannot know why that is - potentially because the server side event got dropped due to some filtering logic on your end.
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
8.36
Framework Version
Next 15 canary
Link to Sentry event
https://paragraph.sentry.io/issues/5850530388/?project=6606494&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&statsPeriod=14d&stream_index=3
Reproduction Example/SDK Setup
Steps to Reproduce
I'm running Next 15 canary and the latest Sentry NextJS SDK (8.36).
I have the onRequestError configured in instrumentation.ts as per these docs, and I'm also properly importing the corresponding server/edge configs via instrumentation as per these docs.
Despite doing that, I'm still getting the stacktrace & error messages omitted in React server component errors.
Expected Result
The full stacktrace should be included.
Actual Result
The stacktrace and error message is omitted:
An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details