TypeError: The "payload" argument must be of type object. Received null when using ImageResponse

[github0013]

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/typeerror-the-payload-argument-must-be-of-type-object-received-null-when-usi-pzgs64

To Reproduce

1. Create the following file: /app/opengraph-image.tsx

import { ImageResponse } from "next/og";

export default async function Image() {
  return new ImageResponse(<div>{`aaa`} 🎉</div>, {
    width: 1200,
    height: 630,
  });
}

2. Start the Next.js development server
3. Access http://localhost:3000/opengraph-image in a browser.

• It is worth to mention that when 🎉 is removed, it works without an error.

Current vs. Expected behavior

Current

⨯ [Error: TypeError: The "payload" argument must be of type object. Received null
at cloneSourceMapV3 (node:internal/source_map/source_map:365:3)
at new SourceMap (node:internal/source_map/source_map:145:21)
at findSourceMap (node:internal/source_map/source_map_cache:339:17)
at getSourcemappedFrameIfPossible (/app/node_modules/next/dist/server/patch-error-inspect.js:163:90)
at parseAndSourceMap (/app/node_modules/next/dist/server/patch-error-inspect.js:265:39)
at sourceMapError (/app/node_modules/next/dist/server/patch-error-inspect.js:288:22)
...
...

This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
] {
code: 'ERR_INTERNAL_ASSERTION',
page: '/opengraph-image'
}

Expected

The page shows aaa 🎉 as an image.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #144-Ubuntu SMP Fri Feb 7 20:47:38 UTC 2025
  Available memory (MB): 31902
  Available CPU cores: 8
Binaries:
  Node: 20.17.0
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.1.7 // Latest available version is detected (15.1.7).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: standalone

Which area(s) are affected? (Select all that apply)

Metadata, Dynamic Routes

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

[akorchyn]

+1

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[pacorroX]

Yeah, just happened me when I added this SVG:

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 2000 2000">
        <path
            d="m65,1638.61c0-13.99.82-27.8,2.43-41.36,8.59-36.61,18.93-72.55,30.91-107.72,72.12-211.72,203.99-395.8,375.52-532.13l.02-.02c18.35-14.59,37.14-28.62,56.38-42.08.01-.01.02-.02.04-.02,30.82-16.15,65.89-25.28,103.09-25.28,49.33,0,94.91,16.05,131.8,43.23.54.39,1.07.78,1.59,1.18.2.14.39.29.59.44,40.2,30.36,69.77,74.05,82.13,124.5,3.96,16.14,6.15,32.97,6.37,50.27.01.32.01.63.01.94.01.65.01,1.29.01,1.94,0,.78,0,1.56-.02,2.34-.69,68-31.9,128.7-80.59,169.05-9.26,6.24-18.36,12.69-27.29,19.36,0,0,0,0,0,.01-33.3,24.86-64.27,52.65-92.54,83.01-43.62,46.81-80.8,99.68-110.14,157.23h753.09c121.5,0,220,98.5,220,220v4c0,121.5-98.5,220-220,220H400.94c-24.28-.9-47.93-4.28-70.7-9.9-127.66-31.48-227.65-133.19-256.67-261.79-3.81-16.87-6.4-34.2-7.66-51.9-.61-8.35-.91-16.79-.91-25.3Z"
            fill="currentColor"/>
        <path
            d="m1934.39,362.89c0,13.99-.82,27.8-2.43,41.36-8.59,36.61-18.93,72.55-30.91,107.72-72.12,211.72-203.99,395.8-375.52,532.13l-.02.02c-18.35,14.59-37.14,28.62-56.38,42.08-.01.01-.02.02-.04.02-30.82,16.15-65.89,25.28-103.09,25.28-49.33,0-94.91-16.05-131.8-43.23-.54-.39-1.07-.78-1.59-1.18-.2-.14-.39-.29-.59-.44-40.2-30.36-69.77-74.05-82.13-124.5-3.96-16.14-6.15-32.97-6.37-50.27-.01-.32-.01-.63-.01-.94-.01-.65-.01-1.29-.01-1.94,0-.78,0-1.56.02-2.34.69-68,31.9-128.7,80.59-169.05,9.26-6.24,18.36-12.69,27.29-19.36,0,0,0,0,0-.01,33.3-24.86,64.27-52.65,92.54-83.01,43.62-46.81,80.8-99.68,110.14-157.23h-753.09c-121.5,0-220-98.5-220-220v-4c0-121.5,98.5-220,220-220h897.45c24.28.9,47.93,4.28,70.7,9.9,127.66,31.48,227.65,133.19,256.67,261.79,3.81,16.87,6.4,34.2,7.66,51.9.61,8.35.91,16.79.91,25.3Z"
            fill="currentColor"/>
    </svg>

Using 15.1.7

[psimk]

duplicate of #75580?

[github0013]

duplicate of #75580?

#75580 (comment)

Fixed in #75713

https://github.com/vercel/next.js/releases/tag/v15.2.0-canary.48

Handle invalid sourcemaps: #75713

using "next": "v15.2.2-canary.3", but it still gets the error.
https://codesandbox.io/p/devbox/typeerror-the-payload-argument-must-be-of-type-object-received-null-when-usi-pzgs64?file=%2Fapp%2Fopengraph-image.tsx%3A4%2C40-4%2C43

Maybe this is an edge case of the fix #75713?

[CarrettaRiccardo]

Somehow i get this error when using firebase-admin with collectionGroup queries:

 const result = await firebaseAdminFirestore
    .collectionGroup("user-settings")
    .where("token_verify_email", "==", token)
    .get();

• next@15.4.0.canary.91 (using --turbo)
• firebase-admin@13.4.0 (tried also with version 12, same issue)

⚠️ It only happens with .where() queries

❌ Error

file:///Users/rick/Documents/Projects/portfolio/node_modules/@google-cloud/firestore/build/src/telemetry/enabled-trace-util.js:
Invalid source map. Only conformant source maps can be used to find the original code.
Cause: TypeError [ERR_INVALID_ARG_TYPE]: The "payload" argument must be of type object. Received null

Error: 9 FAILED_PRECONDITION: 
     at handler (src/app/api/test/route.ts:20:9)
     at <unknown> (src/lib/validate-api.ts:169:21)
   18 |         .collectionGroup("user-settings")
   19 |         .where("token_verify_email", "==", token)
 > 20 |         .get();
      |         ^
   21 |     } catch (error) {
   22 |       console.error(error);
   23 |     } {
   code: 9,
   details: '',
   metadata:  {
      internalRepr: Map(1) { 'x-debug-tracking-id' => [ '13907992341687480348;o=1' ] },
      options: {}
    }
 }

EDIT: it may be caused by a thrown error of firebase-admin when collection indexes are required for the query - but instead this weird error is shown.

[devjiwonchoi]

Reported upstream at nodejs/node#59653, the fix for this issue was landed at Node.js v22.14.0. Could you guys try a version or higher and see if it resolves?