Describe the bug
When a user attempts to log in with invalid credentials (e.g., an email address that is not registered), the system displays a cascade of numerous, identical, generic error notifications ("Something went wrong" and "Failed to login") instead of a single, clear error message.
To Reproduce
Steps to reproduce the behavior:
- Navigate to the login page.
- Enter an email address that is not registered with the application.
- Enter any password.
- Click the "Login" button.
- Observe the multiple error notifications that appear and overlap on the screen.
Expected behavior
When login fails due to invalid credentials, the application should display one clear, concise, and user-friendly error message, such as "Invalid email or password. Please try again or register."
Actual behavior
A large number of identical, generic error messages ("Something went wrong" / "Failed to login") are triggered and displayed simultaneously, overwhelming the user interface and providing no specific feedback about why the login failed.
Screenshots
Additional context
This is a significant user experience (UX) bug. The excessive and unhelpful error messages make the application appear unstable. The root cause is likely an issue in the frontend error handling logic, possibly an infinite loop or repeated state updates triggered by the failed login attempt. The error handling needs to be refactored to show only a single, appropriate message per failed attempt.
Describe the bug
When a user attempts to log in with invalid credentials (e.g., an email address that is not registered), the system displays a cascade of numerous, identical, generic error notifications ("Something went wrong" and "Failed to login") instead of a single, clear error message.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When login fails due to invalid credentials, the application should display one clear, concise, and user-friendly error message, such as "Invalid email or password. Please try again or register."
Actual behavior
A large number of identical, generic error messages ("Something went wrong" / "Failed to login") are triggered and displayed simultaneously, overwhelming the user interface and providing no specific feedback about why the login failed.
Screenshots
Additional context
This is a significant user experience (UX) bug. The excessive and unhelpful error messages make the application appear unstable. The root cause is likely an issue in the frontend error handling logic, possibly an infinite loop or repeated state updates triggered by the failed login attempt. The error handling needs to be refactored to show only a single, appropriate message per failed attempt.