Issue with Account Login Failure When Using Prisma, Expo, and genericOAuth
Hello,
I'm currently observing a strange and interesting behavior that I’d like to report.
Although I'm using Nest.js in my project, I’ve confirmed that the same issue also occurs when using Express.
The steps to reproduce the bug are fairly simple:
Once the first OAuth login is completed, the application keeps logging in with that same initial account—even when attempting to log in with a different account.
This behavior persists across all devices. Regardless of which device you use to log in, the app keeps authenticating with the original account.
What’s even more confusing is that when using
I don’t know the exact cause, but it seems to be some kind of bug with Prisma.
Once I stopped using Prisma, the issue disappeared.
I'm currently observing a strange and interesting behavior that I’d like to report.
Although I'm using Nest.js in my project, I’ve confirmed that the same issue also occurs when using Express.
The steps to reproduce the bug are fairly simple:
- Set up Prisma.
- Set up Expo.
- Log in via OAuth (using genericOAuth).
- The order of these steps does not matter.
Once the first OAuth login is completed, the application keeps logging in with that same initial account—even when attempting to log in with a different account.
This behavior persists across all devices. Regardless of which device you use to log in, the app keeps authenticating with the original account.
What’s even more confusing is that when using
mapProfileToUser and logging the profile data, everything appears to be working correctly.I don’t know the exact cause, but it seems to be some kind of bug with Prisma.
Once I stopped using Prisma, the issue disappeared.
