-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AuthException Not returning valid message and status code for banned_until As per documentation #1745
Comments
you must be stupid to think that u can do this, I hope you get banned. Edit: They have banned this person, Well deserved. Now waiting for a response on the ticket above. |
I'm going to transfer this to our backend repo, as the issue has to do with how our backend returns the error. |
Hey team, Thanks for flagging this - this is a known issue and has been recently patched. Fix is here for reference It will likely go out before next week |
Oh man thanks, Could i get notified so i can make the required from my end? |
did this go live on the stable version? |
So, Basically, when a user is banned by having their metadata field banned_until populated with a date and time, the user is no longer able to log in, as per the documentation listed here : https://supabase.com/docs/reference/dart/auth-error-codes
There is a clear section of the various errors that can be returned, one of which is called user_banned, you can scroll below to find it).
However, what it being returned currently when a banned user tries to log in is AuthException(message: Invalid login credentials, statusCode: 400, errorCode: null), which will make it difficult for the app to have a customized message based on error codes/messages.
To Reproduce Quickly
Steps to reproduce the behavior:
Expected behavior
To return Valid error codes based on documentation
sample code to catch auth exception
Version (please complete the following information):
Latest version of Supabase:2.3.0, supabase_flutter: 2.6.0
Would love to get some feedback on this.
The text was updated successfully, but these errors were encountered: