Enatega Customer App: App Crashes and Shows White Screen When Adding a New Address (e.g., "F10")
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, react-native
- Domain
- mobile
Research direction
Start by reproducing the customer app address flow: open the address section, choose “Add a New Address,” enter “F10,” and tap Save or Continue. Inspect the handling of this input and verify that the address is saved without a crash or white screen, with the user redirected or shown confirmation.
Written by the indexing model from the issue text.
Description
Describe the bug
When a user attempts to add a new address by clicking the "Add a New Address" button and enters an address such as "F10", the app crashes and displays a white screen. No error message or feedback is shown, leaving the user stuck.
Steps to Reproduce:
Open the app and go to the address section.
Tap on "Add a New Address."
Enter a new address like "F10".
Tap Save or Continue.
Observe the app behavior.
Expected behavior
The address should be saved successfully, and the user should be redirected to the previous screen or receive a confirmation message.
Smartphone (please complete the following information):
Device: [e.g. Samsung A15]
OS: [e.g. Android]
Browser [e.g. App]
Version [e.g. Android Version 15]
Additional context
Add any other context about the problem here.
Labels: Enatega Multivendor Customer App, High Priority, Bug
- 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