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
{{ message }}
Repository navigation
PPR - Static bail out error caught when using partial prerending nextjs #12061
Sentry.init({dsn: process.env.SENTRY_DSN,// Adjust this value in production, or use tracesSampler for greater controltracesSampleRate: 1,// Setting this option to true will print useful information to the console while you're setting up Sentry.debug: false,// Uncomment the line below to enable Spotlight (https://spotlightjs.com)// spotlight: process.env.NODE_ENV === 'development',});
Sentry catches errors for routes that use ppr.
This is the error description:
Route /location/les-caves-du-roy-nightclub needs to bail out of prerendering at this point because it used headers. React throws this special object to indicate where. It should not be caught by your own try/catch. Learn more: https://nextjs.org/docs...
Hello, can you try to put the content of sentry.server.config.ts into instrumentation.ts? In v8, the Sentry setup on server and edge should be done in instrumentation.ts and the old config files can be deleted.
I just want to make sure that this is not a setup-related problem. I hope this will help :)
hey @s1gr1d moved my logic to instrumentation.ts, the error can still be reproduced. I am pretty sure your Node wrapper is catching this error.
import*asSentryfrom"@sentry/nextjs";exportasyncfunctionregister(){if(process.env.NEXT_RUNTIME==="nodejs"){Sentry.init({dsn: "https://bf65eb7c9c42794495d4916d58a78477@o4507254924115968.ingest.de.sentry.io/4507254931259472",// Adjust this value in production, or use tracesSampler for greater controltracesSampleRate: 1,// Setting this option to true will print useful information to the console while you're setting up Sentry.debug: false,// Uncomment the line below to enable Spotlight (https://spotlightjs.com)// spotlight: process.env.NODE_ENV === 'development',});}if(process.env.NEXT_RUNTIME==="edge"){Sentry.init({dsn: "https://bf65eb7c9c42794495d4916d58a78477@o4507254924115968.ingest.de.sentry.io/4507254931259472",// Adjust this value in production, or use tracesSampler for greater controltracesSampleRate: 1,// Setting this option to true will print useful information to the console while you're setting up Sentry.debug: false,});}}
Activity
s1gr1d commentedon May 16, 2024
Hello, can you try to put the content of
sentry.server.config.tsintoinstrumentation.ts? In v8, the Sentry setup on server and edge should be done ininstrumentation.tsand the old config files can be deleted.I just want to make sure that this is not a setup-related problem. I hope this will help :)
Link to the docs
andrewdoro commentedon May 20, 2024
hey @s1gr1d moved my logic to instrumentation.ts, the error can still be reproduced. I am pretty sure your Node wrapper is catching this error.
andrewdoro commentedon May 20, 2024
Also this should not be caught - from Next.js docs

AbhiPrasad commentedon May 27, 2024
Fix released with https://github.com/getsentry/sentry-javascript/releases/tag/8.5.0 - please give it a try!