TRPCClientError: Unexpected token 'A', "An error o"... is not valid JSON

I'm making a

fetch

fetch

API call to an external server inside a tRPC route.
It works perfectly on localhost, but never works when deployed on Vercel.
The request normally takes ~30s, and it has a large body (~12KB).

Solution

I worked around this by upgrading my API server to process it in under 10s, so this confirms it's a timeout issue.

Jump to solution

Codex•3/5/24, 9:08 PM

It might be that vercel is timing out if you don't have the pro version

CCodex It might be that vercel is timing out if you don't have the pro version

MochaOP•3/5/24, 9:52 PM

I pay for Pro

Bumble•3/6/24, 7:24 AM

maybe it has something to do with your middleware file?

BBumble maybe it has something to do with your middleware file?

MochaOP•3/6/24, 2:32 PM

I haven't made any modifications to my trpc.tstrpc.ts file (Pages router)

Bumble•3/6/24, 3:06 PM

I meant middleware.tsmiddleware.ts at the root of your project. Make sure the request actually gets to your trpc handler. When I got this error, middleware.tsmiddleware.ts was redirecting requests to sign in page.

BBumble I meant `middleware.ts` at the root of your project. Make sure the request actua...

MochaOP•3/6/24, 5:11 PM

Right, but I don't have a middleware.tsmiddleware.ts in this project since I'm using Pages Router, not App Router

Solution

Mocha•3/7/24, 3:53 PM

I worked around this by upgrading my API server to process it in under 10s, so this confirms it's a timeout issue.

TRPCClientError: Unexpected token 'A', "An error o"... is not valid JSON

Similar Threads

Similar Threads

Similar Threads