Unknown arg provider_providerAccountId in where.provider_providerAccountId for type accountWhereUniqueInput. Available args:

[HT-Moh]

Environment

System:
OS: Linux 5.13 Ubuntu 20.04.4 LTS (Focal Fossa)
CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Memory: 11.93 GB / 30.99 GB
Container: Yes
Shell: 5.8 - /usr/bin/zsh
Binaries:
Node: 16.14.2 - /usr/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 8.1.2 - /usr/local/bin/npm
Browsers:
Brave Browser: 100.1.37.116
Chrome: 100.0.4896.127
Firefox: 99.0
npmPackages:
next: 12.1.5 => 12.1.5
next-auth: ^4.3.3 => 4.3.3
react: ^18.0.0 => 18.0.0

Reproduction URL

#3631

Describe the issue

I upgraded and I followed https://next-auth.js.org/getting-started/upgrade-v4#database-migration but now I am getting the following when synchronize = true

and the following when synchronize: true :

"@next-auth/typeorm-legacy-adapter": "^0.1.2-next.20", "next": "12.1.5", "next-auth": "^4.3.3",

I went back import { PrismaAdapter } from "@next-auth/prisma-adapter"
same issue.

I made sure that the schema as per 2 guides I follow but no.
first one: https://next-auth.js.org/getting-started/upgrade-v4#schema-changes
second one: https://next-auth.js.org/getting-started/upgrade-v4#database-migration

Really confusing which adapter to choose and even what is the write schema.

I had the same problem a while back and I made everything work and now after upgrading the app naturally everything stopped working.

I have 2 simple questions:
Which adapter needs to be used TypeORMLegacyAdapter or '@next-auth/prisma-adapter' ?
What is the correct schema?

How to reproduce

here is the final schema, but I tested all possible schema I found

model account {
  id                Int      @id(map: "accounts_pkey") @default(autoincrement())
  userId            Int
  type              String
  provider          String
  providerAccountId String
  refresh_token     String?
  access_token      String?
  expires_at        String?
  created_at        DateTime @default(now()) @db.Timestamptz(6)
  updated_at        DateTime @default(now()) @db.Timestamptz(6)
  session_state     String?
  id_token          String?
  scope             String?
  token_type        String?
  user              user     @relation(fields: [userId], references: [id], onUpdate: Restrict)
}
model sessions {
  id           Int      @id @default(autoincrement())
  expires      String
  sessionToken String
  created_at   DateTime @default(now()) @db.Timestamptz(6)
  updated_at   DateTime @default(now()) @db.Timestamptz(6)
  userId       Int
  user         user     @relation(fields: [userId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "fk_user_id")
}
model user {
  id                Int                 @id(map: "users_pkey") @default(autoincrement())
  name              String?
  email             String              @unique(map: "users_email_key")
  emailVerified     String?
  image             String?
  created_at        DateTime            @default(now()) @db.Timestamptz(6)
  updated_at        DateTime            @default(now()) @db.Timestamptz(6)
  is_admin          Boolean             @default(false)
  twitter           String?
  avatar            String?
  title             String?
  first_name        String?
  last_name         String?
  facebook          String?
  github            String?
  project_id        Int?
  projects          projects?           @relation(fields: [project_id], references: [id], onDelete: Restrict, onUpdate: Restrict, map: "users_project_id_fkey")
  account           account[]
  blog_author       blog_author[]
  comment           comment[]
  minter_collection minter_collection[]
  sessions          sessions[]
}

model verification_tokens {
  id         Int      @id(map: "verification_requests_pkey") @default(autoincrement())
  identifier String
  token      String   @unique(map: "verificationtokens_token_key")
  expires    String
  created_at DateTime @default(now()) @db.Timestamptz(6)
  updated_at DateTime @default(now()) @db.Timestamptz(6)
}

Expected behavior

it should just work

[Lucasnribeiro]

Did you found a solution?

[HT-Moh]

Actually, almost every time I updated the library I have such issues, the fields change often and their names do not follow the naming convention for DB, another issue is the last version of prisma, npx prisma db pull cmd seems to override the @map so I needed to update the DB to make everything works
Here is what works for me on next-auth 4.15.0 prisma 4.5.0 @next-auth/prisma-adapter 1.0.5
change table name accounts to account
change table name users to user
change attribute on provider_account_id to providerAccountId
change FK user_id to userId (FK on account table)
change attribute email_verified to emailVerified on user table
Make provider and providerAccountId unique
On Hasura if you have to delete a unique make sure the index is deleted as well otherwise it prevents you from setting unique again.
last steps npx prisma db pull && npx prisma generate

[teddybee]

I have the same issue with @next-auth/prisma-adapter": "^1.0.7, "@prisma/client": "^4.15.0" and sqlite.

Unknown arg provider_providerAccountId in where.provider_providerAccountId for type AccountWhereUniqueInput. Did you mean `providerId_providerAccountId

[hyoloui]

../node_modules/@next-auth/prisma-adapter/dist/index.js:211:45

  208 getUserByEmail: (email) => p.user.findUnique({ where: { email } }),
  209 async getUserByAccount(providerAccountId) {
  210     var _a;
→ 211     const account = await p.account.findUnique({
            where: {
              providerAccountId: {
              ~~~~~~~~~~~~~~~~~
                providerAccountId: '11111111',
                provider: 'github'

Changing the schema will still cause the problem.

[ManishBisht777]

model Account {
    id                 String    @id @default(cuid())
    userId             String
    providerType       String
    providerId         String
    role               String
    providerAccountId  String
    refreshToken       String?
    accessToken        String?
    accessTokenExpires DateTime?
    createdAt          DateTime  @default(now())
    updatedAt          DateTime  @updatedAt
    user               User      @relation(fields: [userId], references: [id])

    @@unique([providerId, providerAccountId])
    @@index([userId])
}

model Session {
    id           String   @id @default(cuid())
    userId       String
    expires      DateTime
    sessionToken String   @unique
    accessToken  String   @unique
    role         String
    createdAt    DateTime @default(now())
    updatedAt    DateTime @updatedAt
    user         User     @relation(fields: [userId], references: [id])

    @@index([userId])
}

model User {
    id            String    @id @default(cuid())
    name          String?
    email         String?   @unique
    emailVerified DateTime?
    image         String?
    role          String
    createdAt     DateTime  @default(now())
    updatedAt     DateTime  @updatedAt
    accounts      Account[]
    sessions      Session[]
}

model VerificationRequest {
    id         String   @id @default(cuid())
    identifier String
    token      String   @unique
    expires    DateTime
    createdAt  DateTime @default(now())
    updatedAt  DateTime @updatedAt

    @@unique([identifier, token])
}

This is my Prisma schema and i am still getting the

Unknown argument provider_providerAccountId. Did you mean providerId_providerAccountId? Available options are listed in green. PrismaClientValidationError:
Invalid prisma.account.findUnique() invocation:

{
  where: {
    provider_providerAccountId: {
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
      providerAccountId: "113802192673870361114",
      provider: "google"
    },
?   id?: String,
...

[mugidar]

Did you solve it?

[hyoloui]

No…hahaha

…

2023. 7. 24. 오후 6:12, Manish Bisht ***@***.***> 작성: model Account { id String @id <https://github.com/id> @default <https://github.com/default>(cuid()) userId String providerType String providerId String role String providerAccountId String refreshToken String? accessToken String? accessTokenExpires DateTime? createdAt DateTime @default <https://github.com/default>(now()) updatedAt DateTime @updatedAt user User @relation <https://github.com/relation>(fields: [userId], references: [id]) @@unique([providerId, providerAccountId]) @@Index([userId]) } model Session { id String @id <https://github.com/id> @default <https://github.com/default>(cuid()) userId String expires DateTime sessionToken String @unique <https://github.com/unique> accessToken String @unique <https://github.com/unique> role String createdAt DateTime @default <https://github.com/default>(now()) updatedAt DateTime @updatedAt user User @relation <https://github.com/relation>(fields: [userId], references: [id]) @@Index([userId]) } model User { id String @id <https://github.com/id> @default <https://github.com/default>(cuid()) name String? email String? @unique <https://github.com/unique> emailVerified DateTime? image String? role String createdAt DateTime @default <https://github.com/default>(now()) updatedAt DateTime @updatedAt accounts Account[] sessions Session[] } model VerificationRequest { id String @id <https://github.com/id> @default <https://github.com/default>(cuid()) identifier String token String @unique <https://github.com/unique> expires DateTime createdAt DateTime @default <https://github.com/default>(now()) updatedAt DateTime @updatedAt @@unique([identifier, token]) } This is my Prisma schema and i am still getting the Unknown argument provider_providerAccountId. Did you mean providerId_providerAccountId? Available options are listed in green. PrismaClientValidationError: Invalid prisma.account.findUnique() invocation: { where: { provider_providerAccountId: { ~~~~~~~~~~~~~~~~~~~~~~~~~~ providerAccountId: "113802192673870361114", provider: "google" }, ? id?: String, — Reply to this email directly, view it on GitHub <#4653 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3S5FEZTTX2NA57V7RSMAQDXRY36ZANCNFSM6AAAAAAQO27P6Y>. You are receiving this because you commented.

[nicoalbanese]

I just encountered this as I was using the template schema from the next-auth documentation with the new authjs/prisma-adapter. There are some slight changes in schema, and once I used the template from the new documentation, it all worked as expected.
New docs: https://authjs.dev/reference/adapter/prisma#prismaadapter
Old docs: https://next-auth.js.org/v3/adapters/prisma

[KeturahDev]

This saved me as well! Thanks!

[Alex87464]

It worked for me too, thank you!

[deepakyadav20322]

It works for me, thanks.

[dimerbwimba]

This works for me thanks @estevanjantsk

[mustafazuberiexp]

It worked for me too, thank you!

[mugidar]

God bless you! пт, 8 сент. 2023 г. в 21:10, Nico ***@***.***>:

…

I just encountered this as I was using the template schema from the next-auth documentation with the new authjs/prisma-adapter. There are some slight changes in schema, and once I used the template from the new documentation, it all worked as expected. New docs: https://authjs.dev/reference/adapter/prisma#prismaadapter Old docs: https://next-auth.js.org/v3/adapters/prisma — Reply to this email directly, view it on GitHub <#4653 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHJOOQFOW3A357XCIAT5ETXZNNSZANCNFSM6AAAAAAQO27P6Y> . You are receiving this because you commented.Message ID: ***@***.***>

[umanda]

Despite exploring various solutions, the issue persists. For context, I'm working with the following versions in my project:

next: 14.1.0
next-auth: ^4.24.6
@next-auth/prisma-adapter: ^1.0.7
@prisma/client: ^5.10.2

After encountering this challenge, I decided not to spend much time on it. Instead, I opted for a more flexible approach by implementing a Custom Adapter. This has given me full control over the authentication process. While this workaround suits my current needs, I'm still interested in any insights or solutions that might address the original issue with the prescribed setup.

I appreciate any guidance or feedback from the community.

[isabelleilyia]

Do you mind sharing your solution? Would be much appreciated :)

[umanda]

Certainly,

In my scenario, I utilise an external API as my backend infrastructure. To integrate this effectively, I devised a bespoke adaptor, detailed as follows in my my-adaptor.ts file:

import axios from "axios";

export async function apiService(url: string, body: any) {
  try {
    const { data } = await axios.post(
      url,
      body,
      { headers: { "Content-Type": "application/json" } }
    );
    return data;
  } catch (err: any) {
    throw new Error(err.message || "Something went wrong.");
  }
}

/** @return { import("next-auth/adapters").Adapter } */
export function MyAdapter() {
  return {
    async createUser(user: any): Promise<any> {
      const request = await apiService("<API endpoint>", {<data>});
      return request;
    },

    async test(id: any): Promise<any> {
      return;
    },

    async template(updatedUser: any): Promise<any> {
      return;
    },
  };
}

// Configuration for NextAuth options
export const options: NextAuthOptions = {
  adapter: MyAdapter(),
  // ... the remainder of your code
};

This custom adaptor is pivotal for the seamless integration with NextAuth, facilitating user creation and other operations by communicating with the external API. It exemplifies a tailored solution for specific backend requirements, ensuring that the application remains flexible and maintainable.

This approach only for my custom need. you may get idea from this.