-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: Cannot read properties of undefined (reading 'call') #70703
Comments
@JClackett Thank you for submitting an issue! I was not able to replicate the issue when deployed on Vercel.
Is the |
@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. |
@JClackett Can you share a screenshot (or recording) when you receive this error? Not able to replicate it even sporadically. |
I used to get the same error randomly when using redirect in a server action. I have never been able to reproduce 100%. In my case, it's in a form. I store data in DB and then redirect to form next page B, then it sometimes throw, and when it does I need to refresh the page A, and click again to go to next form page B. EDIT:
|
Same for me. It's very random... |
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
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
and
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.
The text was updated successfully, but these errors were encountered: