Error toasts display raw JavaScript objects instead of user-friendly messages

[latifniz]

Problem
When an error occurs, the toast notifications display raw JavaScript objects (e.g., Error: {message: 'Invalid request', code: 400}) instead of concise and user-friendly error messages. This makes it difficult for users to understand the issue and take corrective action.

Expected Behavior
Toast notifications should display clean, user-readable error messages such as:

"Invalid request. Please check your input."
"Failed to load data. Try again later."
Steps to Reproduce
Perform an action that triggers an error (Login

).
Observe the error toast notification displayed on the screen.
Note that the toast contains the raw JavaScript object instead of a proper message.
Proposed Solution
Parse the error response and display only the relevant message (e.g., error.message or a predefined friendly message).
Use fallback messages for unknown or unhandled errors (e.g., "An unexpected error occurred. Please try again.").