Description
On application startup, the system checks for existing user authentication details. If no valid session is found, it should automatically initiate a guest login process. -> this much is already implemented in client.js.
During the login process, and until a definitive response is received from the server (either success or error), the application must display a loading screen to indicate that authentication is in progress.
If the login attempt fails for any reason (e.g., server unreachable, timeout, invalid response), the application should gracefully handle the failure by displaying an appropriate and user-friendly error message.
Expected Behavior
- Check for stored login credentials on startup
- If none are found, initiate guest login automatically
- Display a loading screen while awaiting server response
- On successful login → proceed to the main application
- On failure → display a clear and relevant error message
Notes
- Ensure the loading state persists strictly until a response is received
- Handle edge cases such as network failures, server downtime, and unexpected responses
- Error messages should be informative but not overly technical
Description
On application startup, the system checks for existing user authentication details. If no valid session is found, it should automatically initiate a guest login process. -> this much is already implemented in
client.js.During the login process, and until a definitive response is received from the server (either success or error), the application must display a loading screen to indicate that authentication is in progress.
If the login attempt fails for any reason (e.g., server unreachable, timeout, invalid response), the application should gracefully handle the failure by displaying an appropriate and user-friendly error message.
Expected Behavior
Notes