Serverside type error

I am using react + nextjs as my tech stack. After successfully building my application, when I run the project using

pnpm run start

pnpm run start

pnpm run start

pnpm run start, it works fine initially. However, when I interact with Supabase through front-end, I encounter the error shown in the attached image, which causes the application to crash. Strangely, if I refresh the page, the application starts working again.

I am unsure why this issue occurs. From the error message, I can see that it is a type-related error, but I do not know how to debug it, as it appears to be a server-side issue. My client-side build is functioning correctly. Moreover, this error does not consistently appear after following specific steps or making particular changes, making it difficult to debug or reproduce the issue.

janglad•1/30/25, 11:52 AM

what version of next/supabase are you using? I've seen issues made on the githubs for both of these about this

heetOP•1/30/25, 11:55 AM

"@supabase/ssr": "^0.5.2",
"@supabase/supabase-js": "^2.46.2",`

heetOP•1/30/25, 11:56 AM

"next": "15.0.3"

Marcus•1/30/25, 12:09 PM

but I do not know how to debug it, as it appears to be a server-side issue

You trytry whatever can throw an exception and you catchcatch any errors and log them to the console. If you're not doing any error handling it's no wonder you don't know what's going on.

Rough guess, something with body already being consumed may be an api route.

heetOP•1/30/25, 12:21 PM

But everything works nicely in the local (dev mode) without any error even in the run time but this issue happens only if I test after deployment

Marcus•1/30/25, 12:53 PM

That’s expected

Marcus•1/30/25, 12:54 PM

Uncaught errors don’t crash in dev mode

heetOP•1/30/25, 12:55 PM

Then what do you sugges like I am new at supabase so what should I do?

Marcus•1/30/25, 1:31 PM

Not to be rude but what do you want anyone here to do? As mentioned if you aren’t even doing basic error handling, how are we suppose to know your call stack? You’ve also shared 0 code, and 0 steps to reproduce?

How do you know it's a supabase issue?

vick•1/30/25, 4:50 PM

Your error is not showing anything supabase related. You are trying to read the data from a Reponse object multiple times: see where it says "alread been consumed"? That's what that is. Like makl says you need to show code and add some error checking to it.

janglad•2/2/25, 9:37 AM

For what it's worth this could actually be down to Supabase internals https://github.com/vercel/next.js/discussions/69635

GitHub

[PPR] TypeError: Response.clone: Body has already been consumed. · ...

@wyattjoh , @ztanner Testing out PPR and PFPR and it seems to be working well for the most part (nice work). However, in one of my routes I am seeing a 500 for the prefetch RSC GET request. Clickin...

Jjanglad For what it's worth this could actually be down to Supabase internals https://gi...

Marcus•2/2/25, 11:13 AM

But that's with PPR experimental feature flag enabled to be fair

janglad•2/2/25, 11:13 AM

Yeah idk I ran into this as well with that disabled

janglad•2/2/25, 11:14 AM

Altho hasn’t shown up in a good bit

janglad•2/2/25, 11:14 AM

But yeah I think this also might have been an issue with Next itself

Serverside type error

Similar Threads

Similar Threads

Similar Threads