[Next.js]: Sentry should not catch trackDynamicDataAccessed

[typeofweb]

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

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[lforst]

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!

[typeofweb]

Next.js version is 14.3.0-canary.53 (only canary versions support PPR).

To reproduce, enable PPR and create a page that uses params and searchParams. See: https://github.com/typeofweb/sentry-nextjs-bug-repro