Wrong location of restaurant displayed while proceeding to order in check out.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript, react-native
- Domain
- mobile
Research direction
Start by reproducing the checkout flow on Windows in Chrome: select a restaurant, proceed to checkout, and inspect the map location for Food-Corner-East. Trace the checkout map entry point and compare its restaurant or order location with the nearby-restaurant result. Done means the checkout map shows the correct restaurant location or the order location consistently.
Written by the indexing model from the issue text.
Description
Describe the bug
a very out of bound distant location of the restaurant is displayed on the check out section
although the address given for hotel "Food-Corner-East" is Islamabad but while checking out an address/location of india is displayed
To Reproduce
Steps to reproduce the behavior:
your order from the restaurant
Click on 'checkout'
Scroll down the map to see the location and you'll see that that is a very different location from what was displayed while searching for nearby restaurants.
See error
Expected behavior
the location should be exact of the restaurant or either your order location
Screenshots
image
Screenshot 2024-03-11 144935
Desktop (please complete the following information):
OS: Windows
Browser Chrome
Version 122.0.6261.95 (Official Build) (64-bit)
Screenshot 2024-03-11 145007
- 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