Next.js 500 Error logs in development but not in Vercel deploy #8155

TrentHurlbut · 2023-05-17T17:49:47Z

Is there an existing issue for this?

I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
I have reviewed the documentation https://docs.sentry.io/
I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

7.52.1

Framework Version

Next 13.2.3

Link to Sentry event

https://repvue.sentry.io/issues/4189882115/?query=is%3Aunresolved&referrer=issue-stream&stream_index=0

SDK Setup

sentry.client.config.js

Sentry.init({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,

  // Adjust this value in production, or use tracesSampler for greater control
  tracesSampleRate: 1,

  // Setting this option to true will print useful information to the console while you're setting up Sentry.
  debug: true,

  replaysOnErrorSampleRate: 1.0,

  // This sets the sample rate to be 10%. You may want this to be 100% while
  // in development and sample at a lower rate in production
  replaysSessionSampleRate: 0.1,

  // You can remove this option if you're not planning to use the Sentry Session Replay feature:
  integrations: [
    new Sentry.Replay({
      // Additional Replay configuration goes in here, for example:
      maskAllText: true,
      blockAllMedia: true,
    }),
  ],
});

sentry.edge.config.js

Sentry.init({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,

  // Adjust this value in production, or use tracesSampler for greater control
  tracesSampleRate: 1,

  // Setting this option to true will print useful information to the console while you're setting up Sentry.
  debug: false,
});

sentry.server.config.js

Sentry.init({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,

  // Adjust this value in production, or use tracesSampler for greater control
  tracesSampleRate: 1,

  // Setting this option to true will print useful information to the console while you're setting up Sentry.
  debug: true,
});

Steps to Reproduce

Set up a Next.js project to handle error notifications for app in Sentry and connect to local development environment.
Add Vercel integration for deployed project of same app.
Test sample errors in development and deployment; both show up as issues in connected Sentry project.
Test a 500 SSR error in development. This logs in Sentry project issues.
Test same 500 SSR error in Vercel deployment. This does not log in Sentry project.

Expected Result

Both development and deployment log the same 500 SSR error in Sentry project issues.

Actual Result

Hello again :)

Actual result is the 500 SSR error only logs in development and not in the Vercel deploy. I have provided a link to the specific issue.

Here are the only logged errors we are seeing in Vercel associated with the event:

Data
Sentry Logger [log]: Integration installed: LinkedErrors
Sentry Logger [log]: Integration installed: RewriteFrames
Sentry Logger [log]: SDK successfully initialized
TypeError: Cannot read properties of undefined (reading 'length')
    at PerformanceCategoryRating (/var/task/.next/server/pages/companies/[slug].js:1914:20)
    at Wc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at $c (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at Zc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:145)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
TypeError: Cannot read properties of undefined (reading 'length')
    at PerformanceCategoryRating (/var/task/.next/server/pages/companies/[slug].js:1914:20)
    at Wc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at $c (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at Zc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:145)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89) {
  page: '/en/companies/GlobalPayments'
}
RequestId: 6d3accfb-377d-4a7d-889b-82f86704ea9b Error: Runtime exited with error: exit status 1
Runtime.ExitError

and

…ion installed: Console
Sentry Logger [log]: Integration installed: Http
Sentry Logger [log]: Integration installed: Undici
Sentry Logger [log]: Integration installed: OnUncaughtException
Sentry Logger [log]: Integration installed: OnUnhandledRejection
Sentry Logger [log]: Integration installed: ContextLines
Sentry Logger [log]: Integration installed: LocalVariables
Sentry Logger [log]: Integration installed: Context
Sentry Logger [log]: Integration installed: Modules
Sentry Logger [log]: Integration installed: RequestData
Sentry Logger [log]: Integration installed: LinkedErrors
Sentry Logger [log]: Integration installed: RewriteFrames
Sentry Logger [log]: SDK successfully initialized
TypeError: Cannot read properties of undefined (reading 'length')
    at PerformanceCategoryRating (/var/task/.next/server/pages/companies/[slug].js:1914:20)
    at Wc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at $c (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at Zc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:145)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
TypeError: Cannot read properties of undefined (reading 'length')
    at PerformanceCategoryRating (/var/task/.next/server/pages/companies/[slug].js:1914:20)
    at Wc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at $c (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at Zc (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:145)
    at Z (/var/task/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89) {
  page: '/en/companies/GlobalPayments'
}
RequestId: 2728ad40-eab0-4879-837e-7b1d44f8408b Error: Runtime exited with error: exit status 1
Runtime.ExitError

I'm not sure they have anything to do with Sentry, however. Just communicating that an error is happening on the server. There are no other logs related to Sentry or this event. It is almost like it's being ignored.

Is this at all related to this issue?
#6120

The text was updated successfully, but these errors were encountered:

lforst · 2023-05-18T08:50:51Z

Hm, looks like this is a duplicate of #7602.

TrentHurlbut · 2023-05-18T11:09:52Z

I think you're right. Still no solve then?

lforst · 2023-05-19T09:46:32Z

Gotta look into this. I am like 99.999% sure this worked at some point. Maybe vercel changed something or we have a regression.

Just to confirm: This happens when throwing in a basic server component right? Do you use the edge runtime?

TrentHurlbut · 2023-05-19T11:36:55Z

Yes to both.

Thank you for digging into this!

avnerI · 2023-05-23T11:46:50Z

I'm joining the wait too

github-actions · 2023-06-14T00:23:53Z

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

AbhiPrasad · 2023-07-27T15:59:51Z

Closing this issue for cleanup. Please re-open if this still applies. Thanks!

TrentHurlbut · 2023-09-28T11:43:15Z

@lforst Was there a resolution to this? We had a bug live on our app for three weeks uncaught because of this gap in Sentry's coverage.

lforst · 2023-09-28T15:08:58Z

There are several reasons why I closed this:

I asked a question which wasn't answered. Making it unnecessarily hard for me to debug this.
We had several improvements to the SDK since this issue was opened, some of which likely resolved this.
It's 3 months since stale bot staled this issue and 2 months since Abhi pinged everybody here again before closing.
We don't see anybody else running into this issue.

It's unlucky that the SDK wasn't reporting the error for you but there is no guarantee that the SDK will catch everything. It's also just code after all.

Since a lot of time has passed I recommend updating Next.js and our SDK and report back whether the problem still exists.

TrentHurlbut · 2023-09-28T15:10:29Z

Which question did you ask that wasn't answered? Also, there was somebody else that was running into this issue (@avnerI).

lforst · 2023-09-29T08:19:39Z

@TrentHurlbut My apologies! I missed the "Yes to both".

As for this issue, I unfortunately cannot reproduce it. I am getting errors in Sentry when I throw in an app deployed to Vercel. Would you mind sharing what the error was about that wasn't reported to Sentry?

One thing I can say: If there are any errors happening outside of any handlers, meaning in the global scope, outside of any api routes or server components, these errors will likely not be caught by Sentry. This is a limitation of AWS lambdas which Vercel uses, since they instantly freeze when a request is ended and there is "no time" for Sentry to flush events :(

TrentHurlbut added the Type: Bug label May 17, 2023

getsantry bot added the Status: Untriaged label May 17, 2023

lforst added Package: nextjs Issues related to the Sentry Nextjs SDK and removed Status: Untriaged labels May 18, 2023

github-actions bot added the Waiting for: Team label May 18, 2023

github-actions bot removed the Waiting for: Team label May 19, 2023

github-actions bot added the Waiting for: Team label May 19, 2023

github-actions bot added the Status: Stale label Jun 14, 2023

github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2023

lforst reopened this Jun 21, 2023

github-actions bot removed the Status: Stale label Jun 22, 2023

AbhiPrasad closed this as not planned Won't fix, can't repro, duplicate, stale Jul 27, 2023

github-actions bot removed the Waiting for: Team label Jul 27, 2023

lforst reopened this Jul 31, 2023

lforst closed this as completed Sep 28, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Next.js 500 Error logs in development but not in Vercel deploy #8155

Next.js 500 Error logs in development but not in Vercel deploy #8155

TrentHurlbut commented May 17, 2023 •

edited

Loading

lforst commented May 18, 2023

TrentHurlbut commented May 18, 2023

lforst commented May 19, 2023

TrentHurlbut commented May 19, 2023

avnerI commented May 23, 2023

github-actions bot commented Jun 14, 2023

AbhiPrasad commented Jul 27, 2023

TrentHurlbut commented Sep 28, 2023

lforst commented Sep 28, 2023 •

edited

Loading

TrentHurlbut commented Sep 28, 2023 •

edited

Loading

lforst commented Sep 29, 2023 •

edited

Loading

Next.js 500 Error logs in development but not in Vercel deploy #8155

Next.js 500 Error logs in development but not in Vercel deploy #8155

Comments

TrentHurlbut commented May 17, 2023 • edited Loading

Is there an existing issue for this?

How do you use Sentry?

Which SDK are you using?

SDK Version

Framework Version

Link to Sentry event

SDK Setup

Steps to Reproduce

Expected Result

Actual Result

lforst commented May 18, 2023

TrentHurlbut commented May 18, 2023

lforst commented May 19, 2023

TrentHurlbut commented May 19, 2023

avnerI commented May 23, 2023

github-actions bot commented Jun 14, 2023

AbhiPrasad commented Jul 27, 2023

TrentHurlbut commented Sep 28, 2023

lforst commented Sep 28, 2023 • edited Loading

TrentHurlbut commented Sep 28, 2023 • edited Loading

lforst commented Sep 29, 2023 • edited Loading

TrentHurlbut commented May 17, 2023 •

edited

Loading

lforst commented Sep 28, 2023 •

edited

Loading

TrentHurlbut commented Sep 28, 2023 •

edited

Loading

lforst commented Sep 29, 2023 •

edited

Loading