
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
- Data Diet Needed
I love the nested related data... but can we request limited data? I think my requests need to go on a diet. I return my courses, and the units all come with th...
- Issue in Accessing Cloud from Pakistan
Earlier today I faced an issue accessing cloud services but later on VPN fixed it. Now even with vpn I can't access cloud. When my App tries to create a docume...
- Appwrite Cloud Ui and Server Crashes rep...
I am having trouble with Appwrite cloud and server crashes and Ui crashed repeatedly. Raised a GitHub issue as well. https://github.com/appwrite/appwrite/issues...
