
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
- No mails from Appwrite
Hello, Since severals days, i have a problem : i d'ont received any mails from Appwrite. I'm using the auth by mail and i don't any code so any mails from App...
- dart function very slow
sometimes waiting too long, about 3mins to 5mins, sometimes very fast, not build time, just execute, anyway to speed up?
- wrong code for google oauth2 ?
gives User (role: guests) missing scope (account) error
