-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Next.js]: Sentry should not catch trackDynamicDataAccessed
#11969
Comments
Assigning to @getsentry/support for routing ⏲️ |
Thanks for reporting. We'll look into it! Would you mind sharing your Next.js version, and how to reproduce this? (Normally our issue template asks for this but you opened this in the Sentry product repo instead of the SDK repo) Thanks! |
Next.js version is To reproduce, enable PPR and create a page that uses params and searchParams. See: https://github.com/typeofweb/sentry-nextjs-bug-repro |
Fix released with https://github.com/getsentry/sentry-javascript/releases/tag/8.5.0 - please give it a try! |
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
When Partial Prerendering (PPR) is enabled, using APIs that opt into Dynamic Rendering like cookies, headers, or fetch (such as with cache: 'no-store' or revalidate: 0) will cause React to throw a special error object to know which part of the page cannot be statically generated - while still letting the rest of it be partially static. If you catch this error, it is not safe for us to generate any static data, and your build will fail.
https://nextjs.org/docs/messages/ppr-caught-error
Expected Result
This error is not caught and not reported to Sentry.
Actual Result
This error is caught and reported in Sentry
Product Area
Other
Link
No response
DSN
https://3fe190d9390c9209bdd921874ff01078@o4507230795923456.ingest.us.sentry.io/4507230797955072
Version
No response
The text was updated successfully, but these errors were encountered: