Body is unusable: Body has already been read error

[kyllerss]

I have fairly straight-forward code on one particular endpoint called /push_notifications.json that has the following code:

export async function POST(event: RequestEvent) {

    let user_account_uuid = (event.locals.session)?.user_account?.uuid;
    if (user_account_uuid === undefined)  {
        return json({success: false});
    }

    const form_data = await event.request.formData(); // <- many errors here!
    
    ... // shenanigans

    return json({success: true});
}

I am getting a very high number of errors stating that the body has already been consumed:

Body is unusable: Body has already been read

I can't reproduce this in local Dev environment, this is only occurring in Production. The app is deployed on Vercel. I am wondering if this has something to do with middle-ware being inserted into the stack by Vercel.

Has anyone run into this problem? Is there is anything I can do to alleviate the issue?

[Dragos-P-Popa]

I am experiencing the same issue.

export async function POST({ request }: { request: Request }) {
	const data = await request.json();

        ...

[harshmandan]

Same thing here. Hosted on Gcloud

src/routes/api/[...path]/+server.ts:

export const POST: RequestHandler = async ({ request, params, locals }) => {  
    const args = await request.json()
    // ...
}

[geodask]

It seems unlikely because you said it works locally but could you confirm if there are any hooks in hooks.server.ts/.js that might be accessing the request body? Additionally, are you using adapter-auto? If so, could you try building the application locally and running preview to check if the errors still occur?

[lewis-conroy]

any updates on this?

[kyllerss]

For other reasons since reporting this issue, I migrated my deployment to Railway. I no longer have this issue. As part of this move, I moved to adapter-node - not sure if this is related.

[Dragos-P-Popa]

For other reasons since reporting this issue, I migrated my deployment to Railway. I no longer have this issue. As part of this move, I moved to adapter-node - not sure if this is related.

I have been experiencing the issue with adapter-node.