Next auth not working with PrismaAdapter

[kumard3]

Question 💬

How can i resolve this issue and it is happening with github and google as i have tested with these two only

screenVideo.mov

How to reproduce ☕️

screenVideo.mov

import NextAuth from "next-auth";

import GoogleProvider from "next-auth/providers/google";
import { PrismaAdapter } from "@next-auth/prisma-adapter";
import { PrismaClient } from "@prisma/client";

const prisma = new PrismaClient();

export default NextAuth({
 adapter: PrismaAdapter(prisma),
  providers: [

    GoogleProvider({
      clientId: process.env.GOOGLE_ID,
      clientSecret: process.env.GOOGLE_SECRET,
    }),

  ],
});

and if i comment the adapter: PrismaAdapter(prisma),
the issue is resolved but now my prisma is not working .

Contributing 🙌🏽

No, I am afraid I cannot help regarding this

[cqh963852]

I Have meet same problem. Solved with #3970 (comment)

[eoSalinas]

Worked here! Thanks 😁

[TommyLeong]

I'm facing similar issue now, error of [next-auth][error][adapter_error_getSessionAndUser] .

Using the following dependencies, NextJs 14 app router. Anyone face this too?

   "@auth/prisma-adapter": "^1.6.0",
    "@prisma/client": "^5.12.1",
    "next": "14.1.3",
    "next-auth": "^4.24.7",

Tried with the solution, didn't work either.

session: {
strategy: 'jwt',
},

[kumard3]

can you share your next auth config code

[TommyLeong]

import NextAuth from "next-auth";
import { PrismaAdapter } from "@auth/prisma-adapter";
import prisma from "@app/helper/prisma-client-instance";
import CredentialsProvider from "next-auth/providers/credentials";


const handler = NextAuth({
  adapter: PrismaAdapter(prisma),
  providers: [
    CredentialsProvider({
      name: "Credentials",
      async authorize(credentials, req) {
        try {
          const user = await prisma.users.findUnique({
            where: {
              username: credentials.username,
            },
            select: {
              userID: true,
            },
          });
          if (user) {
            // Any object returned will be saved in `user` property of the JWT
            return user;
          } else {
            console.log("empty record...");
            // If you return null then an error will be displayed advising the user to check their details.
            return null;
          }
        } catch (e) {
          console.log(e);
          console.log(e.message);
        }
      },
      secret: process.env.NEXT_AUTH_SECRET,
      jwt: {
        maxAge: 60 * 60 * 24 * 30,
      },
      session: {
        strategy: "jwt",
        maxAge: 30 * 24 * 60 * 60, // 30 days
      },
      callbacks: {
        async signIn({ user, account, profile, email, credentials }) {
          console.log("callback sigin in");
          return true;
        },
        session({ session, token }) {
          session.user.username = token.user;
          session.user.id = token.id;
          return session;
        },
      },
      pages: {
        signIn: "/",
      },
    }),
  ],
});

export { handler as GET, handler as POST };

Here you go, appreciate your reply. Hopefully you can spot some issue out from it.

[kumard3]

try using this one and have you generated the NEXTAUTH_SECRET

const handler = NextAuth({
  adapter: PrismaAdapter(db),
  providers: [
    CredentialsProvider({
      name: "Credentials",
      credentials: {
        email: { label: "email", type: "text" },
        password: { label: "password", type: "password" },
      },
      type: "credentials",
      authorize: async (credentials) => {
        // Fetch the user from the database based on the provided username
        const user = await db.user.findUnique({
          where: { email: credentials?.email },
        });
        if (user) {
          // Include the desired user properties in the session
          return Promise.resolve(user);
        } else {
          return Promise.resolve(null);
        }
      },
    }),
  ],
  secret: process.env.NEXT_AUTH_SECRET,
  jwt: {
    maxAge: 60 * 60 * 24 * 30,
  },
  session: {
    strategy: "jwt",
    maxAge: 30 * 24 * 60 * 60, // 30 days
  },
  callbacks: {
    async signIn({ user, account, profile, email, credentials }) {
      console.log("callback sigin in");
      return true;
    },
    session: async ({ session, user, token }) => {
      return {
        ...session,
        user: {
          ...(session.user ?? ""),
          id: token.id ?? "",
          email: token.email ?? "",
        },
      };
    },
    jwt: async ({ token, account, user }) => {
      if (account) {
        token.accessToken = account.access_token;
        token.id = user.id;
        token.email = user.email;
        token.image = user.image;
      }
      return token;
    },
  },
  pages: {
    signIn: "/",
  },
});

[SteveSimms]

@kumard3 how did you solve this issue?
I am facing the same behavior with Gmail provider.

[StephenOnyeka]

Most of the time the problem is not particularly on the prisma-adapter, it can just be from the prisma client. If the prisma adapter is defined correctly following the next-auth or auth.js documentation for the authentication,

import NextAuth from "next-auth";
import GoogleProvider from "next-auth/providers/google";
import GithubProvider from "next-auth/providers/github";
import { PrismaAdapter } from "@next-auth/prisma-adapter";
import { PrismaClient } from "@prisma/client";

const prisma = new PrismaClient();

export const authOptions = {
  adapter: PrismaAdapter(prisma),
  providers: [
    GithubProvider({
      clientId: process.env.GITHUB_ID,
      clientSecret: process.env.GITHUB_SECRET,
    }),
    GoogleProvider({
      clientId: process.env.GOOGLE_ID,
      clientSecret: process.env.GOOGLE_SECRET,
    }),
  ],
}
export default NextAuth(authOptions);

After defining your schema.prisma file run npx prisma generate, if you later update or make changes to your schema.prisma file; still run the npx prisma generate command and resolve potential issues shown in the terminal