Rider assigns and picks up an order, but the status does not update in the customer application due to a coordination issue between the rider and customer applications.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- full-stack, mobile-dev
Research direction
Reproduce the flow where a rider assigns an unassigned order and picks it up, then compare the order status shown in the rider and customer-facing applications. Trace the coordination between those application entry points and verify that the customer view changes to the corresponding picked-up or on-the-way status in real time.
Written by the indexing model from the issue text.
Description
Describe the bug
When a rider assigns themselves an order and picks it up, the status of the order (e.g., "Picked Up" or "On the Way") is not updated in the customer-facing application. This results in a discrepancy between the rider's actual status and what the customer sees, creating confusion and potentially affecting the customer experience.
To Reproduce
A rider assigns themselves an unassigned order and picks it up.
The order status should update to "Picked Up" or "On the Way" in the customer application.
Expected behavior
When a rider assigns themselves an order and picks it up, the status in the customer application should update accordingly (e.g., "Picked Up," "On the Way," etc.), reflecting the rider's actual actions in real-time.
Actual behavior
The status in the customer application does not update when the rider assigns and picks up the order, leaving the customer with outdated information.
Smartphone (please complete the following information):
Device: iPhone15pro
OS: iOS17.6.1
Screenshots
IMG_0485
IMG_0486
IMG_0487
Activity
- 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/food-ordering-system-java-eclipse
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
All issues in raymondjames090/food-ordering-system-java-eclipse
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