Case 1
if account was created using the email and password, in that case email is marked not verifed ( this is fine).
Case 2
if login via OAuth services, and if there was no account earlier with the same email then in that case email is marked verified ( this is fine).
Case 3
Now, when user login again using any OAuth service ( google, facebook, apple), and if email address is same in OAuth provider as well, then in that case email should be marked as verified ( this was expected behaviour).
Wonder, why in the case 3 email is not getting marked as verifed when user logging in via OAuth and if account already exist with given email address?
Iβm going to guess it has something to do with separate Identities?
logging via OAuth doesn't tend to create new identity...
Identities are something new in 1.4. we haven't documented them yet π
so just doubt would it create new Identity, but what if email already exist π€
yap, seems this is it
just wondering, that we will go with case 3 no? that describe above? Would be prevent the OAuth login ( because most of custom server implementation does prevent user from Logging if accund was created via email password)
Case 3
Now, when user login again using any OAuth service ( google, facebook, apple), and if email address is same in OAuth provider as well, then in that case email should be marked as verified ( this was expected behaviour).
Recommended threads
- Charged after Downgrade
I downgraded from the pro plan last month, but itβs still trying to charge my card this month and my account has been restricted
- Wifi issue with Pop!_OS linux distro
Hey guys... iam facing this very peculiar trouble with my linux distro... I use Pop!_OS on my HP victus gaming laptop with nvedia 2050 graphics card.... The pro...
- Urgent Help
Hello Appwrite team, I urgently need your help. I am the founder of OnBuch, an EdTech application used by around 10,000 users in Cameroon. In the last two day...