Bug: No Feedback for Unregistered User Login Attempt

[anushkaa2205]

Description

When an unregistered user attempts to log in, the page simply reloads without displaying any error message or guidance.

Current Behavior

• User enters credentials without having an account.
• Page reloads or remains unchanged.
• No feedback/error message is shown.

Expected Behavior

• Display an appropriate error message such as:
  "Account does not exist. Please sign up first."
• Prevent silent page reload.
• Optionally provide a redirect or link to the Sign Up page.

Suggested Fix

• Add frontend validation and proper error handling for invalid/unregistered login attempts.
• Display a toast or inline error message for better user experience.

Additional Notes

Providing proper authentication feedback improves usability and prevents user confusion.

[Sanjay-Hub-Dev]

Hi @Ashmita1206 👋

I would like to work on this issue under GSSoC 2026.

🧩 Issue Understanding

After reviewing the authentication flow, it appears that login attempts using unregistered/non-existent user credentials do not provide clear feedback to the user.

This can create confusion during authentication because users are not properly informed whether the login failed due to invalid credentials or because the account does not exist.

🔍 Implementation Plan

I’m planning to:

• Review the current login error handling flow
• Improve frontend handling for unregistered user authentication responses
• Ensure clear and user-friendly feedback messages are displayed
• Maintain consistency with the existing authentication UI and validation flow
• Preserve current login functionality while improving UX clarity

📂 Files Likely Involved

• Login/authentication page components
• Authentication API handling logic
• Error rendering/notification related sections

✅ Validation

• Test login attempts using unregistered user credentials
• Verify proper error feedback is displayed consistently
• Ensure no regression in existing authentication functionality

I’ll keep the implementation clean, focused, and aligned with the current StackIt authentication workflow.

Please assign this issue to me 🚀