Cancelled Orders Still Visible in Customer App Until App is Restarted
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- mobile-dev
Research direction
No file or test is named. Start by tracing the customer app's order-status update path and the cancellation flow between the store and customer apps, checking the suggested WebSocket events or API refresh. Done means a cancellation changes the open customer's order to “Cancelled” without restarting the app.
Written by the indexing model from the issue text.
Description
Describe the bug
When an order is cancelled from the store app, it still appears as active in the customer app, even though it’s no longer valid. The customer app only reflects the cancellation after the app is completely closed and reopened, indicating that the app isn't updating the order status in real time.
To Reproduce
Steps to reproduce the behavior:
Place an order via the customer app
Cancel the order from the store app
Keep the customer app open and check the order status
Notice that the order still appears active
Close and reopen the customer app
Now the cancellation is reflected
Expected behavior
The customer app should immediately update the order status (e.g., to “Cancelled”) when a store cancels the order, without needing to restart the app.
Screenshots
Smartphone (please complete the following information):
Device: Samsung A15
OS: Android 14
App Version: [insert if known]
Additional context
This is a real-time sync issue—possibly due to missing WebSocket events or untriggered API refresh after status change. It leads to confusion and may result in users contacting support unnecessarily.
Activity
har33m
added the
Bug
issue type 4 days ago
har33m
added
bug
Something isn't working
good first issue
Good for newcomers
Enatega Multivendor Customer App
Urgent!
4 days ago
deepakarthikeya
deepakarthikeya commented 4 days ago
deepakarthikeya
4 days ago
Hi! I would like to take this up and work on a fix. Could you please assign the issue to me?
har33m
har33m commented 4 days ago
har33m
4 days ago
Author
you can work on it! @deepakarthikeya. Happy coding :)
- 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