-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Error serializing ._sentryBaggage
returned from getServerSideProps
#12102
Comments
I came to report the same error. Additional context: Also happens with 8.0.0 and 8.1.0. Specifically only happening with |
I have the same behavior as @samsch and @dorin-flooz. |
I am using next js pages. |
Hi @Nastoc4ka, which instrumentation file are you referring to specifically? |
when you move from 7 to 8, you are creating instrumentation file and removing sentry.server.config.js according to documentation. Did you follow migration guide: https://docs.sentry.io/platforms/javascript/guides/nextjs/migration/v7-to-v8/ |
I have the same issue. I don't have a UPDATE: The moment I amde sentry available to be init every time it started working. If I check for production env, or DSN availability it doesn't. Why? |
Sentry protects against sentry being down. Yes you need to initialize Sentry all the time, but for instance if you pass an empty DSN it disables most of all functionality (eg: sending any error at all). |
Hi, from looking at it it seems that Next.js uses a custom serializer that cannot handle |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
8.2.1
Framework Version
NextJs 14.2.3
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
After upgrading to "@sentry/nextjs": "8.2.1", we get the following error:
When reverting to "@sentry/nextjs": "7.115.0" the error goes away. How can we debug and fix this? Searched for
sentryBaggage
already, but nothing came up.Also - how come we get Sentry errors in our local dev env, when Sentry is explicitly disabled through
enabled: false
in our Sentr.init?Expected Result
Actual Result
The text was updated successfully, but these errors were encountered: