Next. js version 12.3.4, invalid server report, no errors collected；"@sentry/nextjs": "8.13.0"

[parlay96]

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

1： Firstly, the register method on the server was not executed at all，

2： The Sentry platform also did not collect any errors regarding the server side

3：Only client errors are effective for the client

Expected Result

How to solve it?

Actual Result

1： Firstly, the register method on the server was not executed at all，

2： The Sentry platform also did not collect any errors regarding the server side

3：Only client errors are effective for the client

Product Area

Unknown

Link

No response

DSN

No response

Version

"@sentry/nextjs": "8.13.0"

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[aldy505]

Can you confirm that this is only happening with Nextjs and this is not happening on any other language/platforms?

[parlay96]

@aldy505 I'm certainly not sure, but there's this situation next，However, what I have learned is that the next version on my end is 12.xx, which is a version issue

[aldy505]

I don't think this has anything to do with self-hosted. Since Sentry should receive all the data, I guess this is much likely a problem on the SDK itself.

@hubertdeng123 @azaslavsky can we transfer this to sentry-javascript?

[chargome]

Hi @parlay96, as discussed in #12746, Next.js v12 is not supported by "@sentry/nextjs": "8.13.0". Can you confirm that you have downgraded your SDK to v7?

[parlay96]

@chargome Haha, I didn't downgrade，But I know the problem now, it was caused by next 12.xx

[parlay96]

@chargome This is a repetitive question I asked before, and I know how to solve it ， Thank you；We are about to upgrade to 14.xx

[chargome]

Good to hear you were able to resolve it! Upgrading to Next.js v14 is definitely a good idea to ensure ongoing compatibility with Sentry's latest features. Closing this, feel free to ping me if you need more help.

[parlay96]

你好@parlay96，如#12746中所述，Next.js v12 不受支持"@sentry/nextjs": "8.13.0"。您能确认已将 SDK 降级到 v7 吗？

Hi @parlay96, as discussed in #12746, Next.js v12 is not supported by "@sentry/nextjs": "8.13.0". Can you confirm that you have downgraded your SDK to v7?

Hi, I've downgraded to version 7.18, why do I need a second parameter for this?

[parlay96]

@chargome
why do I need a second parameter for this?

[parlay96]

@chargome

When I use withSentryGetServerSideProps, it seems to have become obsolete

[chargome]

Hi @parlay96, not sure if I get your question. withSentryGetServerSideProps has been deprecated in favour of wrapGetServerSidePropsWithSentry.

[parlay96]

@chargome I know, but I would like to know why the second parameter of 'wrappGeserverSidePropsWithSentry' is?

[parlay96]

The document tells me that there is no second parameter

[parlay96]

@chargome I am very grateful to you. Every time I come to see you for help, thank you

[chargome]

In the screenshot you posted you can see it: @param parameterizedRoute The page's parameterized route

[parlay96]

@

In the screenshot you posted you can see it: @param parameterizedRoute The page's parameterized route

Why wasn't the document example written? I am a mandatory item, what is its purpose

[parlay96]

@chargome Thank you, I'm going to follow you now

[chargome]

@parlay96 you're right it should be part of the docs. So you want to pass the the route that will be parameterised there, e.g. /someroute -> it will be used for naming the transaction in Sentry.

[parlay96]

@parlay96 you're right it should be part of the docs. So you want to pass the the route that will be parameterised there, e.g. /someroute -> it will be used for naming the transaction in Sentry.

Thank you

[parlay96]

@chargome

next 12.x sentry7.1.. wrapGetServerSidePropsWithSentry It seems invalid, no errors have been collected,

[parlay96]

@chargome How do I check this question? Do I still need to raise issues for NextJS?

[chargome]

@parlay96 in your code you are catching the error, hence no error is being captured by sentry. You can call Sentry.captureException in your catch block and the error will be sent.

[parlay96]

@chargome I know it is possible to report captureException proactively and it can be implemented. Then why do I need to use 'wrapGetServerSidePropsWithSentry'? Wasn't 'wrapGetServerSidePropsWithSentry' just helping me automatically collect errors

[parlay96]

Is there a problem with my understanding? hahaha

[chargome]

@parlay96 the SDK will report unhandled exceptions. If you want to send specific errors then use Sentry.captureException.

[parlay96]

@chargome

Thank you, I think I know how to use Sentry now

[parlay96]

@chargome ha ha ha , Thank you very much for solving my problem. You are my idol