Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js. #47805

llorenspujol · 2023-04-01T22:38:46Z

Verify canary release

I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 16.19.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.2.4
      eslint-config-next: 13.0.0
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Data fetching (gS(S)P, getInitialProps), Middleware / Edge (API routes, runtime)

Link to the code that reproduces this issue

I cannot reproduce it locally.

To Reproduce

I don't know exactly how to reproduce it locally, it seems to happen only when deployed on Vercel.

Describe the Bug

When executing a serverless function, I am getting the error Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js. approximately 50% of the times. This error seems to happen only when deployed on vercel. I see the error just by checking the logs.
It seems a bug in the cachedData, since this code is what is giving this error: https://github.com/vercel/next.js/pull/46204/files

Here is the Serverless execution success and fail chart by day, almost 50% fails due to this error.

Here is a full error example found in the "Logs":

2023-04-01T22:34:02.255Z	undefined	INFO	info  - Loaded env from /var/task/.env.production
Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js.
    at NextNodeServer.renderToResponseWithComponentsImpl (/var/task/node_modules/next/dist/server/base-server.js:1013:27)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async NextNodeServer.renderPageComponent (/var/task/node_modules/next/dist/server/base-server.js:1072:24)
    at async NextNodeServer.renderToResponseImpl (/var/task/node_modules/next/dist/server/base-server.js:1098:32) {
  page: '/front-end-jobs-in-antwerp'
}
RequestId: 3193f9ce-3d2b-493d-b5f4-6d8c4c407b22 Error: Runtime exited with error: exit status 1
Runtime.ExitError

Expected Behavior

I expect the cache to work as expected and to have no errors in the serveless function executions. My external backend service , where the serverless function gets the data, does not fail, so the expected behaviour is that the serveless function gets the data and cache it as expected.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

_NEXT-1391

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

certmates · 2023-04-12T20:25:15Z

Seeing the same issue, specifically for Google web crawling.

TYPE: Serverless Function

Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js.
    at NextNodeServer.renderToResponseWithComponentsImpl (/var/task/node_modules/next/dist/server/base-server.js:1013:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async NextNodeServer.renderPageComponent (/var/task/node_modules/next/dist/server/base-server.js:1072:24)
    at async NextNodeServer.renderToResponseImpl (/var/task/node_modules/next/dist/server/base-server.js:1098:32) {
  page: 'X'
}
RequestId: X Error: Runtime exited with error: exit status 1
Runtime.ExitError

hk86 · 2023-04-30T11:21:06Z

I'm seeing this as well. Someone found the issue?

iamsoltan · 2023-05-16T14:08:11Z

me too

ijjk · 2023-05-18T05:01:07Z

Hi, can you please confirm this is still an issue in the latest version of Next.js v13.4.3-canary.2? If so please provide a minimal reproduction to allow investigation!

certmates · 2023-05-24T21:28:39Z

Hi @ijjk,

Sorry for the delay. New version broke some unrelated functions for me.

I previously had a ~90% fail rate on requesting Google indexing. I have tried 10 times since updating and it failed just once. I will monitor over the next days.

Thank you.

l-you · 2023-05-30T10:07:02Z

NextJs 13.4.3
Still getting this error sometimes.
Deployment to Vercel.

Error occurs only for User Agent
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Google-PageRenderer Google (+https://developers.google.com/+/web/snippet/)

jmikrut · 2023-05-30T15:47:18Z

We're seeing this quite frequently with our website (https://payloadcms.com) all of a sudden.

It happens on different pages each time we deploy, but typically one of these three pages is broken:

https://payloadcms.com/cloud-pricing
https://payloadcms.com/compare/contentful
https://payloadcms.com/for-enterprise

Pages are broken when you navigate directly to the URLs, but the pages work if you navigate to them via links on the website (in the header / footer via next/link.)

This only happens when deployed to Vercel. Can't reproduce running in production locally.

llorenspujol · 2023-06-04T11:33:11Z

@ijjk still happening with Next.js v13.4.4

jmikrut · 2023-06-06T20:47:04Z

For everyone else's visibility, we opened a Vercel help discussion here:

https://github.com/orgs/vercel/discussions/2677

ijjk · 2023-06-10T22:19:19Z

Hi, this has been updated in v13.4.5 of Next.js please update and give it a try!

austintreneff · 2023-06-16T21:06:01Z

Just a heads up here.. I was still experiencing the issue on v13.4.5 but v13.4.6 seems to have fixed it.

francofantini · 2023-06-20T13:17:36Z

Hi there, I'm still seeing these error logs in production using v13.4.6

Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js.
at NextNodeServer.renderToResponseWithComponentsImpl (/var/task/node_modules/next/dist/server/base-server.js:1274:27)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NextNodeServer.renderPageComponent (/var/task/node_modules/next/dist/server/base-server.js:1333:24)
at async NextNodeServer.renderToResponseImpl (/var/task/node_modules/next/dist/server/base-server.js:1365:32)
at async NextNodeServer.pipeImpl (/var/task/node_modules/next/dist/server/base-server.js:641:25)
at async Object.fn (/var/task/node_modules/next/dist/server/next-server.js:1139:21)
at async Router.execute (/var/task/node_modules/next/dist/server/router.js:315:32)
at async NextNodeServer.runImpl (/var/task/node_modules/next/dist/server/base-server.js:615:29)
at async NextNodeServer.handleRequestImpl (/var/task/node_modules/next/dist/server/base-server.js:546:20) {
page: '/categorias/lamparas'
}
RequestId: 065834d7-2433-4378-8637-e8b243f845c2 Error: Runtime exited with error: exit status 1
Runtime.ExitError

Anyone else?

llorenspujol · 2023-06-22T06:20:11Z

Same, still happening with v13.4.6.

I think we should re-open the issue.

logansparlin · 2023-07-02T02:13:47Z

This is happening for me on v13.4.7

ijjk · 2023-07-05T23:34:45Z

Can anyone reporting this is still occurring provide a deployment or repo with reproduction where they are seeing it?

The confirmed cases of this have all been resolved and are working properly in the latest version of Next.js

steve-marmalade · 2023-07-07T14:08:39Z

@ijjk , here is a deployment running 13.4.9-canary.2 where I am continuing to see this issue: https://web-rcvmm3c6s-marmalade.vercel.app/. The requested URL was https://www.marmalade.co/shop-small?exp=directS2

START RequestId: 6596f190-b28a-45a0-9805-72839a735556 Version: $LATEST
2023-07-06T20:08:18.518Z	6596f190-b28a-45a0-9805-72839a735556	ERROR	Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js.
    at NextNodeServer.renderToResponseWithComponentsImpl (/var/task/node_modules/next/dist/server/base-server.js:1289:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async NextNodeServer.renderPageComponent (/var/task/node_modules/next/dist/server/base-server.js:1348:24)
    at async NextNodeServer.renderToResponseImpl (/var/task/node_modules/next/dist/server/base-server.js:1380:32)
    at async NextNodeServer.pipeImpl (/var/task/node_modules/next/dist/server/base-server.js:641:25)
    at async Object.fn (/var/task/node_modules/next/dist/server/next-server.js:1158:21)
    at async Router.execute (/var/task/node_modules/next/dist/server/router.js:315:32)
    at async NextNodeServer.runImpl (/var/task/node_modules/next/dist/server/base-server.js:615:29)
    at async NextNodeServer.handleRequestImpl (/var/task/node_modules/next/dist/server/base-server.js:546:20) {
  page: '/%7B%22emailVerified%22%3Afalse%2C%22experiment%22%3A%22directS2%22%2C%22isLoggedIn%22%3Afalse%2C%22isWebview%22%3Afalse%7D/shop-small'
}
RequestId: 6596f190-b28a-45a0-9805-72839a735556 Error: Runtime exited without providing a reason
Runtime.ExitError
END RequestId: 6596f190-b28a-45a0-9805-72839a735556
REPORT RequestId: 6596f190-b28a-45a0-9805-72839a735556	Duration: 191.80 ms	Billed Duration: 192 ms	Memory Size: 1024 MB	Max Memory Used: 146 MB

The UserAgent making the request was Googlebot

Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.5735.179 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

This ensures we don't bail from static generation unexpectedly due to a bot request as this shouldn't affect ISR handling. Test deployment with patch can be seen here https://test-app-isr-fallback-dwn2neok6-vtest314-ijjk-testing.vercel.app/new Fixes: #47805

ijjk · 2023-07-12T06:54:40Z

Hi, this has been updated in v13.4.10-canary.3 of Next.js, please update and give it a try!

Galanthus · 2023-07-23T01:45:32Z

Hi, this has been updated in v13.4.10-canary.3 of Next.js, please update and give it a try!

Still not working and returning the same error in production on Vercel. Tested on latest 3 versions.

Galanthus · 2023-07-24T21:45:42Z

Verify canary release

I verified that the issue exists in the latest Next.js canary release

Provide environment information
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 16.19.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.2.4
      eslint-config-next: 13.0.0
      react: 18.2.0
      react-dom: 18.2.0
Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Data fetching (gS(S)P, getInitialProps), Middleware / Edge (API routes, runtime)

Link to the code that reproduces this issue

I cannot reproduce it locally.

To Reproduce

I don't know exactly how to reproduce it locally, it seems to happen only when deployed on Vercel.

Describe the Bug

When executing a serverless function, I am getting the error Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js. approximately 50% of the times. This error seems to happen only when deployed on vercel. I see the error just by checking the logs. It seems a bug in the cachedData, since this code is what is giving this error: https://github.com/vercel/next.js/pull/46204/files

Here is the Serverless execution success and fail chart by day, almost 50% fails due to this error.

Here is a full error example found in the "Logs":
2023-04-01T22:34:02.255Z	undefined	INFO	info  - Loaded env from /var/task/.env.production
Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js.
    at NextNodeServer.renderToResponseWithComponentsImpl (/var/task/node_modules/next/dist/server/base-server.js:1013:27)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async NextNodeServer.renderPageComponent (/var/task/node_modules/next/dist/server/base-server.js:1072:24)
    at async NextNodeServer.renderToResponseImpl (/var/task/node_modules/next/dist/server/base-server.js:1098:32) {
  page: '/front-end-jobs-in-antwerp'
}
RequestId: 3193f9ce-3d2b-493d-b5f4-6d8c4c407b22 Error: Runtime exited with error: exit status 1
Runtime.ExitError
Expected Behavior

I expect the cache to work as expected and to have no errors in the serveless function executions. My external backend service , where the serverless function gets the data, does not fail, so the expected behaviour is that the serveless function gets the data and cache it as expected.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

NEXT-1391

Have you ever managed to solve this?

BorisBarzotto · 2023-07-28T23:38:22Z

Error occurs in 13.4.10 too

TrustyTechSG · 2023-08-10T01:59:52Z

Error occurs in 13.4.13. randomly see error below from vercel log.

Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js.

TrustyTechSG · 2023-08-10T02:24:26Z

Error occurs in 13.4.13. randomly see error below from vercel log.

Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js.

Just found out in my case, this error only happen when opening the site in puppeteer.

github-actions · 2023-08-24T12:01:48Z

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

llorenspujol added the bug Issue was opened via the bug report template. label Apr 1, 2023

github-actions bot added area: app App directory (appDir: true) Pages Router Related to Pages Router. Runtime Related to Node.js or Edge Runtime with Next.js. labels Apr 1, 2023

ijjk closed this as completed Jun 10, 2023

timneutkens reopened this Jul 4, 2023

timneutkens added the linear: next Confirmed issue that is tracked by the Next.js team. label Jul 4, 2023

ijjk mentioned this issue Jul 12, 2023

Fix ISR case with bot requests #52581

Merged

ijjk closed this as completed in #52581 Jul 12, 2023

github-actions bot added the locked label Aug 24, 2023

github-actions bot locked as resolved and limited conversation to collaborators Aug 24, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js. #47805

Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js. #47805

llorenspujol commented Apr 1, 2023 •

edited by padmaia

Loading

certmates commented Apr 12, 2023 •

edited

Loading

hk86 commented Apr 30, 2023

iamsoltan commented May 16, 2023

ijjk commented May 18, 2023 •

edited

Loading

certmates commented May 24, 2023

l-you commented May 30, 2023 •

edited

Loading

jmikrut commented May 30, 2023 •

edited

Loading

llorenspujol commented Jun 4, 2023

jmikrut commented Jun 6, 2023

ijjk commented Jun 10, 2023

austintreneff commented Jun 16, 2023

francofantini commented Jun 20, 2023

llorenspujol commented Jun 22, 2023

logansparlin commented Jul 2, 2023

ijjk commented Jul 5, 2023

steve-marmalade commented Jul 7, 2023

ijjk commented Jul 12, 2023

Galanthus commented Jul 23, 2023

Galanthus commented Jul 24, 2023

Verify canary release

Provide environment information

Which area(s) of Next.js are affected? (leave empty if unsure)

Link to the code that reproduces this issue

To Reproduce

Describe the Bug

Expected Behavior

Which browser are you using? (if relevant)

How are you deploying your application? (if relevant)

BorisBarzotto commented Jul 28, 2023

TrustyTechSG commented Aug 10, 2023 •

edited

Loading

TrustyTechSG commented Aug 10, 2023

github-actions bot commented Aug 24, 2023

Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js. #47805

Error: invariant: Expected pageData to be a string for app data request but received undefined. This is a bug in Next.js. #47805

Comments

llorenspujol commented Apr 1, 2023 • edited by padmaia Loading

Verify canary release

Provide environment information

Which area(s) of Next.js are affected? (leave empty if unsure)

Link to the code that reproduces this issue

To Reproduce

Describe the Bug

Expected Behavior

Which browser are you using? (if relevant)

How are you deploying your application? (if relevant)

certmates commented Apr 12, 2023 • edited Loading

hk86 commented Apr 30, 2023

iamsoltan commented May 16, 2023

ijjk commented May 18, 2023 • edited Loading

certmates commented May 24, 2023

l-you commented May 30, 2023 • edited Loading

jmikrut commented May 30, 2023 • edited Loading

llorenspujol commented Jun 4, 2023

jmikrut commented Jun 6, 2023

ijjk commented Jun 10, 2023

austintreneff commented Jun 16, 2023

francofantini commented Jun 20, 2023

llorenspujol commented Jun 22, 2023

logansparlin commented Jul 2, 2023

ijjk commented Jul 5, 2023

steve-marmalade commented Jul 7, 2023

ijjk commented Jul 12, 2023

Galanthus commented Jul 23, 2023

Galanthus commented Jul 24, 2023

Verify canary release

Provide environment information

Which area(s) of Next.js are affected? (leave empty if unsure)

Link to the code that reproduces this issue

To Reproduce

Describe the Bug

Expected Behavior

Which browser are you using? (if relevant)

How are you deploying your application? (if relevant)

BorisBarzotto commented Jul 28, 2023

TrustyTechSG commented Aug 10, 2023 • edited Loading

TrustyTechSG commented Aug 10, 2023

github-actions bot commented Aug 24, 2023

llorenspujol commented Apr 1, 2023 •

edited by padmaia

Loading

certmates commented Apr 12, 2023 •

edited

Loading

ijjk commented May 18, 2023 •

edited

Loading

l-you commented May 30, 2023 •

edited

Loading

jmikrut commented May 30, 2023 •

edited

Loading

TrustyTechSG commented Aug 10, 2023 •

edited

Loading