Login Fails for All Emails Except Demo Customer Email

Open
#771 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, javascript
Domain
authentication, mobile-dev

Research direction

Start by reproducing the failure in the customer app with a registered email other than the demo account, then trace the email login flow through its authentication configuration and backend user validation. Done means valid registered users can log in successfully without relying on the pre-configured demo email.

Written by the indexing model from the issue text.

Description

Describe the bug
In the customer app, users are unable to log in using any email address other than the pre-configured demo customer email. Attempts to log in with a valid registered email result in an error or no response, effectively locking out real users.

To Reproduce
Steps to reproduce the behavior:

Open the customer app
Go to the email login screen
Enter any email other than the demo email (e.g., testuser@gmail.com)
Enter a valid password and attempt to log in
Observe that the login fails with an error
Expected behavior
Users should be able to log in with any valid, registered email address, not just the demo account.

Screenshots

XRecorder_20250619_04.mp4
Smartphone (please complete the following information):

Device: Samsung A15

OS: Android 14

Additional context
This issue may be caused by hardcoded logic tied to the demo account, authentication configuration errors, or backend user validation bugs. It critically affects usability and needs to be resolved to enable access for real customers.

Dominant language
JavaScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raymondjames090/food-ordering-system-java-eclipse

All issues in raymondjames090/food-ordering-system-java-eclipse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.