[Bug] Prisma 2 adapter return wrong User model on "getUserByProviderAccountId"

[sondh0127]

next-auth/src/adapters/prisma/index.js

Line 81 in 07ef3d5

return prisma[Account].findOne({ where: { compoundId: getCompoundId(providerId, providerAccountId) } })

It should return User model instead of Account like the TypeOrm adapter did

next-auth/src/adapters/typeorm/index.js

Line 170 in 07ef3d5

return manager.findOne(User, { [idKey]: account.userId })

[iaincollins]

Sorry for the delay in responding to this (it's been a busy week!)

Thanks for reporting this bug.

[lovettbarron]

Grateful that this was found.
I think I'm getting the same error where the session's userId is referencing the AccountID instead of the User id.

[next-auth][debug][prisma_update_session] {
  id: 19, // Session id
  userId: 3, // Maps to account id
  expires: 2020-12-02T21:24:40.349Z,
  sessionToken: sdfsdfsdf
  accessToken: asdfsdfsdf
  createdAt: 2020-09-03T21:24:40.350Z,
  updatedAt: 2020-09-03T21:24:40.350Z
}

[next-auth][error][session_error] TypeError: Cannot read property 'name' of null
    at /node_modules/next-auth/dist/server/routes/session.js:99:26

[iaincollins]

@readywater As a quick up date, we've merged in a fix, but it's not live yet - it will go out with some other fixes in the next release (I hope in the next few days)!

[lovettbarron]

Now that I know what it is, I've just updated the Session entry with the appropriate userid so I can do the work. Looking forward to the fix and thank you for this awesome library. I'm actually testing it out for a larger existing application and really love what I see.

[lovettbarron]

Hi @iaincollins, quick question: is there an easy way to pull a beta release of this fix into NPM? Or would you suggest just forking + building? Again, grateful for the work you guys are doing on this!

[madx]

Hi @iaincollins , any news about the availability of this fix? I've been bitten by the bug as well: getting a session upon signup works but once I try to sign in again it can't find the user since I switched user IDs to cuids (which is otherwise working fine by the way)

[lovettbarron]

Hi @iaincollins , any news about the availability of this fix? I've been bitten by the bug as well: getting a session upon signup works but once I try to sign in again it can't find the user since I switched user IDs to cuids (which is otherwise working fine by the way)

FYI i ended up forking and just importing that into NPM.
Just take a look at the commits to package, etc for the changes you'll need to make.
https://github.com/stupidsystems/next-auth/

[madx]

FYI i ended up forking and just importing that into NPM.
Just take a look at the commits to package, etc for the changes you'll need to make.
https://github.com/stupidsystems/next-auth/

Thanks for your input, since the bug seems to reside mostly in the Prisma adapter I think I'm just gonna create a custom fork of the adapter to void having to maintain my own.

[github-actions]

🎉 This issue has been resolved in version 3.2.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀