Next JS 14 Error: TypeError: e._formData.get is not a function using Appwrite Backend

Errors in the Console with the Second Submit:

⨯ TypeError: e._formData.get is not a function at AsyncLocalStorage.run (node:async_hooks:330:14) at AsyncLocalStorage.run (node:async_hooks:330:14) at AsyncLocalStorage.run (node:async_hooks:330:14)

Error on Page with the Second Submit: Unhandled Runtime Error Error: e._formData.get is not a function

Call Stack tn file:///D:/projects/jorgelig-labs/wapp-conecta/wapp-conecta-app/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js (35:301625) t.decodeReplyFromBusboy file:///D:/projects/jorgelig-labs/wapp-conecta/wapp-conecta-app/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js (35:306021) <unknown>

Btw, it's best to use 3 back ticks with multi-line code. See https://www.markdownguide.org/extended-syntax/#syntax-highlighting

So if you commented out the Appwrite line and console log, it works?

I can confirm that appwrite is causing this error .. I have been trying to get the Appwrite to work with next.js server actions for a while now. It's disappointing.. This bug is easily reproducible, can someone look into this? It would be nice to get it working...

yes if you comment out appwrite stuff it works.. nothing to do with formdata extraction

Could this be related? https://github.com/vercel/next.js/discussions/53827

Also, what's the code for client sign up?

Where do those logs (accessed at, prefs, etc.) come from?

different issue I think

his code is probably dead right here __const result = await client.signUp(email, password, name); __ and I'm certain that he's calling account.create() via appwrite sdk.. The first call will go through .. the 2nd time you will get the infamous e._formData.get is not a function... the funny thing is.. this error message is so confusing and misleading..

Oh wait...you're not the original poster...would you please create a separate issue with your info please?

im not

but i have exactly the same problem

i have this problem half a year ago.. and i didn't report it

with next.js 13.4

now next.js 14.. still same problem unresolved

I'm writing coding a another commercial next.js appwrite project hoping to use server action .. but seems like it's still not working

can I just use this space... i dont wanna write another post.. the errors are the same

No please. It's best to keep a thread focused on one problem for one user. Otherwise, we may end up trying to debug multiple people's code in a single thread which can get confusing

im not posting my code..

i just used his

ok.. but if it will help you get to the bottom of this i will

i guess not many people using appwrite for next.js?

once you use server action with appwrite you will instantly get this weird error....