Skip to content

Authentication Workflow Fails During Account Creation with Generic Error Message #416

@abcdeep16

Description

@abcdeep16

🐛 Issue Title

Authentication Workflow Fails During Account Creation with Generic Error Message


Summary

The account creation/authentication workflow is currently not functioning as expected. After filling in valid user details and attempting to create an account, the application displays a generic error message:

“Something went wrong. Please try again.”

without providing meaningful feedback or completing the signup process successfully.

This impacts the onboarding flow and prevents users from creating accounts reliably.


Current Behavior

  • User enters username, email, and password

  • Clicking “Create Account” triggers an error state

  • Generic error message is displayed

  • No clear indication of:

    • validation failure
    • API failure
    • authentication issue
    • backend/network error

Expected Behavior

  • Account should be created successfully for valid credentials
  • Proper validation and API responses should be handled gracefully
  • User should receive meaningful error feedback if signup fails
  • Authentication workflow should redirect/continue correctly after successful signup

Possible Causes

  • Backend authentication/API integration issue
  • Improper error handling in signup workflow
  • Missing validation or incorrect request payload
  • Firebase/Auth configuration issue
  • Failed async state handling

Suggested Improvements

  • Improve authentication error handling
  • Add detailed validation messages
  • Add loading states during signup
  • Improve debugging/logging for failed requests
  • Ensure successful redirect/session creation after signup

✅ Acceptance Criteria

  • Users can create accounts successfully with valid inputs
  • Proper validation errors are displayed when necessary
  • Generic error states are replaced with meaningful feedback
  • Signup workflow completes without breaking UI state
  • Authentication flow behaves consistently across different browsers/devices

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions