3 replies

TRPC and protectedProcedure with next-auth

Has anyone ever experienced an issue with a new t3 app with next-auth and trpc where a

protectedProcedure

protectedProcedure

protectedProcedure

protectedProcedure for a mutation stays pending and multiple session requests are also pending when you're signed in?

I've also added a log to the middleware on the

enforceUserIsAuthed

enforceUserIsAuthed

enforceUserIsAuthed

enforceUserIsAuthed and it never seems to get called.
Also, when this happens I have to remove the .next folder and start the dev server again, otherwise clearing the site data and hard refreshing doesn't even load the page anymore.

The procedure works when it's a

publicProcedure

publicProcedure

publicProcedure

publicProcedure

test: protectedProcedure.mutation(({ ctx }) => {
    console.log("ctx", ctx);
    return { data: ctx.session.user, status: 200 };
  }),

test: protectedProcedure.mutation(({ ctx }) => {
    console.log("ctx", ctx);
    return { data: ctx.session.user, status: 200 };
  }),

test: protectedProcedure.mutation(({ ctx }) => {
    console.log("ctx", ctx);
    return { data: ctx.session.user, status: 200 };
  }),

test: protectedProcedure.mutation(({ ctx }) => {
    console.log("ctx", ctx);
    return { data: ctx.session.user, status: 200 };
  }),

TRPC and protectedProcedure with next-auth

Similar Threads

Similar Threads

Similar Threads