T
tRPC

TRPC vanilla client load failed when called on mobile browser

TRPC vanilla client load failed when called on mobile browser

BBryan3
View on Discord
8/25/2023
Hi, I have created a vanilla client to use TRPC without hooks in a NextJS project: 
import { createTRPCProxyClient, httpBatchLink } from "@trpc/client";
import type { AppRouter } from "~/server/api/root";
import SuperJSON from "superjson";

export const trpcClient = createTRPCProxyClient<AppRouter>({
  links: [
    httpBatchLink({
      url: "http://localhost:3000/api/trpc",
    }),
  ],
  transformer: SuperJSON,
});
import { createTRPCProxyClient, httpBatchLink } from "@trpc/client";
import type { AppRouter } from "~/server/api/root";
import SuperJSON from "superjson";

export const trpcClient = createTRPCProxyClient<AppRouter>({
  links: [
    httpBatchLink({
      url: "http://localhost:3000/api/trpc",
    }),
  ],
  transformer: SuperJSON,
});
When I call const res = await trpcClient.example.hello.query({ text: "123" }); It works on desktop, but when using a mobile browser (tested on iOS safari and chrome), the following error is returned with no additional information being logged: 
Unhandled Runtime Error 
TRPCClientError: Load failed
Unhandled Runtime Error 
TRPCClientError: Load failed
Is the error an issue with how the vanilla client is created and how might I be able to fix it? Thanks for your help!

Looking for more? Join the community!

T
tRPC

TRPC vanilla client load failed when called on mobile browser

Join Server
Recommended Posts
`createCaller` and RSC - with next-authI've been upgrading my trpc routers and handlers to support edge+app router with drizzle and next-auuseQuery always fetching when active on pageHi, I was call my procedure like this, using NextJs (page directory) const { isLoading, isError, isSnextjs app router `fetchRequestHandler`'s createContext doesn't run.Hey there, I have the following code: ```ts // /src/app/api/trpc/[trpc]/route.ts import { fetchRequ"Unable to transform response from server" when 401 error returned from middleware (sometimes)I'm trying to figure out a problem where some (a few, not most) 401 error responses result in an unc