Open sumtzehern opened 2 weeks ago
@sumtzehern I am unable to reproduce this behaviour, please can you provide further steps to reproduce this.
This would happen when a user type in a Unregistered username, email would work fine.
Ok, thanks - I've updated the description of the issue with further clarifications regarding this behaviour. If you'd like to submit a PR for this, please feel free to do so. Otherwise, since this isn't a valid use case (we don't support non-email address usernames), this will likely not be prioritised.
How are you running Flagsmith
Describe the bug
Currently, when a user attempts to sign in with an unregistered account, the application displays a generic "Server Error (500)" message in the toast notification. This error message is not user-friendly and does not provide helpful information to the user.
Steps To Reproduce
foo
/bar
).Expected behavior
The application should display a toast notification with a clear and user-friendly error message, such as "Username provided is not a valid email."
Screenshots