TypeError: Cannot read properties of undefined (reading 'call')

[JClackett]

Link to the code that reproduces this issue

https://github.com/JClackett/next-server-actions

To Reproduce

Getting this consistently in production only and only for certain users

TypeError: Cannot read properties of undefined (reading 'call')

message: Cannot read properties of undefined (reading 'call'),
name: TypeError,
stack: TypeError: Cannot read properties of undefined (reading 'call') at l
(<url>/_next/static/chunks/webpack-0062ff542f3d788d.js?

I posted an issue a while back and am still struggling to get a repro, but it's consistently happening. I can see its happening on certain actions but when I test those in production it doesnt error, so im assuming its something to do with a user's browser maybe?

#67208

Looking into the sources there's one webpack file generated and there are 2 references to .call

try {
            f[e].call(n.exports, n, n.exports, l),
            r = !1
        } finally {
            r && delete d[e]
        }

and

   l.o = function(e, t) {
        return Object.prototype.hasOwnProperty.call(e, t)
    },

I can see from the session replays that the server action isnt even being called, it throws an error on the client straight away as soon as the form is submitted.

Current vs. Expected behavior

Server actions dont throw exceptions

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 8
Binaries:
  Node: 18.20.4
  npm: 10.7.0
  Yarn: 1.22.19
  pnpm: 8.15.7
Relevant Packages:
  next: 14.2.14 // Latest available version is detected (14.2.14).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.2
Next.js Config:
  output: N/A

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

Navigation, Runtime, Webpack

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

Vercel (Deployed)

Additional context

Deployed on vercel, production only.

[samcx]

@JClackett Thank you for submitting an issue!

I was not able to replicate the issue when deployed on Vercel.

so im assuming its something to do with a user's browser maybe?

.call() is supported by many browsers, so not sure if that is the case.

Is the supposed to replicate the error all the time?

[JClackett]

@samcx Not all the time no, it seems to happen very sporadically for me.

yeah but what is .call() being called on in this webpack file?

for example, in:

f[e].call(n.exports, n, n.exports, l),

f[e] could be returning undefined.

[samcx]

@JClackett Can you share a screenshot (or recording) when you receive this error? Not able to replicate it even sporadically.