upgraded to new ct3a; all trpc calls throwing 'Unexpected token r in JSON at position 0'
I'm not really sure what the correct context would be to provide here. The error I'm getting is attached.
The query fn isn't even being invoked in the first place, so I suspect this is occurring somewhere in my trpc config. The only trpc code I've touched was adding clerk to the contexts, but I don't see any errors here. Types are all fine as well it seems.
8 Replies
i should state i am using app router
@jack did you mange to figure it out I got the same thing just now
I didn’t sadly I just gave up
I need to take another look soon
Bad Questions
An article by Josh
Yea Idc about this question anymore lol
@jack @vrba if any of you figured this out i'm also in the same issue rn
I’m back to considering moving to remix for the 3rd time
It’s been long enough that I can’t remember why I gave up on remix
I fixed my problem i had an auth middleware that was doing a 307 redirect and breaking call
Try making the trpc call with something like postmen and check what do you get back or call the api from the client and check network