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
- Project restoration button in console
The project restore button in console is taking no effect, i have tried several times and still nothing, it gives same popup if i reload
- SGP region: console returns 401 for all ...
Cloud console cannot open my projects in the Singapore (SGP) region. All console requests return HTTP 401, plus a 503 on analytics.appwrite.io. - Account email...
- Auth not working
guys my appwrite auth isnt working? oauth works (Sign in with google n discord) i have 2 websites deployed where do i get help when i do sign in with email and ...