π Hello! Iβm encountering an unexpected behavior when creating a user in Appwrite.
π Issue:
β’ I first created a user using Google OAuth.
β’ Then I tried to create a user with the same email using email/password.
β’ Instead of receiving the expected 409 user_already_exists error, I received:
AppwriteException: general_bad_request
There was an error processing your request. Please check the inputs and try again. (400)
However:
β If I first create a regular email/password account and then try to create another email/password account with the same email, I correctly receive a 409 user_already_exists error.
β Question:
Why am I getting a 400 Bad Request instead of a 409 user_already_exists when the email is already registered via OAuth?
Is this expected behavior or a bug?
βοΈ Environment: β’ Appwrite: 1.6.1 (self-hosted) β’ SDK: Flutter 15.0.0
Thanks in advance for your help! π
Recommended threads
- Getting error when trying to add domain ...
we use self hosted appwrite on my company and every single time ever I tried to add a domain it shows this error on the top rigth: "Cannot read properties of un...
- Using OTP Email to verify user for passw...
Has anyone ever implemented this? If you did what was your aproach? Did you write an appwrite function?
- Transaction and Session
I've been debugging for hours a problem that now I think it's because It's not allowed: In my project a user log in using the `node-appwrite` SDK (SSR) I store...