
Suppose user first uses email/pass for log in using xyz@gmail.com, few month later on decides to use google oauth2 with same xyz@gmail.com
(or in reverse order)
but appwrite will prevent this saying user already exist, is there any way to overcome this?
why needed: sometime user forgets password and quickly want to login using oauth2

This isn't the intended behavior
https://appwrite.io/docs/references/cloud/client-web/account#createOAuth2Session

...the server will attempt to look for a user with the same email address as the email received from the OAuth2 provider and attach the new session to the existing user. If no matching user is found - the server will create a new user.
Recommended threads
- Get current users team
Hey for one of my use cases I need to get my current logged in user's team. But by default the scope to read the team is not added. ``` const appwriteClient...
- How to reduce DB Reads?
I just noticed that I hit the 500k db reads limit on my very small next js app with the most data being present in one collection having around 50 documents. ...
- Getting issue while migrating from Self ...
i try to migrating my project but when do this error come and dont allow to crate that migration
