Margaret-Petersen / Margaret-Petersen/uber-eats-clone-using-react-native
Cannot Edit Phone Number from Profile After Entering Wrong OTP — Stuck on Verification Screen
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
On the Enatega Multivendor website, when updating the phone number from the profile section, if the OTP entered during verification is incorrect, the user is unable to go back and change the number. The screen stays stuck on OTP verification with no option to edit the phone number or restart the process.
To Reproduce
Steps to reproduce the behavior:
Go to Profile in the Enatega Multivendor website.
Edit the phone number and request OTP verification.
Enter an incorrect OTP.
Try to change the phone number or go back.
Notice that the screen remains stuck on OTP verification without any option to edit the number.
Expected behavior
Users should be able to go back and edit the phone number if the OTP is incorrect, so they can retry with the correct number.
Desktop (please complete the following information):
OS: [Desktop]
Browser [e.g. chrome]
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 Website, 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 at the Profile phone-number update flow and reproduce the incorrect-OTP case on the Enatega Multivendor website. Trace the entry point into OTP verification and the available navigation or retry actions; done means an incorrect OTP no longer traps the user and they can edit the number or restart verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100