Margaret-Petersen / Margaret-Petersen/python-based-food-ordering-system
API error message displayed to user during phone number verification
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When entering an OTP for phone number verification from the Profile section, a backend error message is shown to the user:
Unknown argument "otp" on field "Mutation.sendOtpToPhoneNumber".
This indicates that the API request payload does not match the backend schema, and the error is not being handled gracefully.
To Reproduce
Steps to reproduce the behavior:
Go to Profile.
Add a phone number and request OTP verification.
Enter the OTP.
Observe the error message displayed in grey over the OTP input area.
Expected behavior
The API request should accept the correct parameters and successfully verify the OTP.
If an error occurs, display a user-friendly message (e.g., "Invalid OTP, please try again.") instead of backend error text.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
Labels: Enatega Multivendor Customer App, Bug
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue through Profile phone-number verification: add a phone number, request an OTP, and submit it. Trace the request for Mutation.sendOtpToPhoneNumber and compare its payload with the backend schema, then check the OTP error rendering. Done means verification uses accepted parameters and backend errors are replaced with a user-friendly message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100