-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Prisma 2 adapter return wrong User model on "getUserByProviderAccountId" #559
Comments
Sorry for the delay in responding to this (it's been a busy week!) Thanks for reporting this bug. |
Grateful that this was found.
|
@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)! |
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. |
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! |
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. |
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. |
🎉 This issue has been resolved in version 3.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
next-auth/src/adapters/prisma/index.js
Line 81 in 07ef3d5
It should return User model instead of Account like the TypeOrm adapter did
next-auth/src/adapters/typeorm/index.js
Line 170 in 07ef3d5
The text was updated successfully, but these errors were encountered: