Lack of Navigation Option After Phone Number Already Registered Error - Enatega Multivendor Customer App
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, react-native
- Domain
- mobile
Research direction
Start by tracing the React Native email signup flow on iOS, focusing on the screen that handles the OTP response and the already-registered phone error. Reproduce the flow with an existing phone number and observe the navigation after dismissing the error. Done means the user can return to correct the phone number or choose another signup method without restarting the entire process.
Written by the indexing model from the issue text.
Description
Describe the bug
In the Enatega Multivendor Customer App, there is an issue encountered during the signup process through email. When attempting to sign up with an email and phone number that is already registered, the user receives an error message after entering the OTP received via email. However, upon closing this error message, the app redirects the user back to the home/signup page without providing an option to return to the previous screen. Consequently, users are forced to restart the signup procedure from the beginning.
To Reproduce
Steps to reproduce the behavior:
Begin the signup process through email.
Enter a phone number that is already registered.
Proceed to enter the OTP received via email.
Encounter the error message stating the phone number is already registered.
Close the error message.
Expected behavior
Upon closing the error message, users should be provided with an option to navigate back to the previous screen to correct the phone number or proceed with a different signup method.
Screenshots
RPReplay_Final1710306636.MP4
Smartphone:
Device: iOS
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from raymondjames090/uber-eats-app-clone-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2069 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2003 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raymondjames090/uber-eats-app-clone-using-react-native#2002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#1979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
raymondjames090/uber-eats-app-clone-using-react-native#1978 ·
All issues in raymondjames090/uber-eats-app-clone-using-react-native
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100