Hey hey. OAuth2 authentication (GitHub provider) throws a general_bad_request error when attempting to log in after account deletion through dashboard.
Steps to Reproduce:
- Set up OAuth2 authentication with GitHub provider
- Successfully log in once using OAuth2
- Delete the user account through the Appwrite dashboard
- Attempt to log in again using the same OAuth2 method
Current Behavior:
- Receiving general_bad_request error when trying to log in
- Authentication fails to complete
Expected Behavior:
- Should create a new account and complete authentication successfully
- This worked correctly ~2.5 months ago
TL;DR
OAuth2 login with GitHub shows "general_bad_request" error post deletion via dashboard. Issue arises upon re-login attempt after account deletion. Previously functioning correctly. Solution: Refresh OAuth2 tokens or ask users to reauthenticate post deletion to resolve the error.Recommended threads
- SELF HOSTING ISSUE, DATA NOT MIGRATING T...
Hey, devs, I recently tried to migrate my cloud instance to a self hosted version but my data is not transferred fully only the table structure is transferred ...
- unlike any other provider, your sites DN...
your nameservers dont work with a funny little CNAME error, which is a weird bug but thats what you get when you try to be the kitchen sink, funny errors.
- Weird Table Causes Console to break
I dont even know how this even happened looks like the $createdAt and , $id got switched? <@831428608895615056>