Notification Discrepancy Between Rider and Restaurant Apps
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, react-native
- Domain
- mobile
Research direction
Start by tracing the notification flow between the Enatega rider and restaurant apps when a rider accepts an order. Compare it with the existing customer notification for rider assignment and identify where the restaurant notification should be handled. Done means the restaurant receives an assignment notification with the relevant rider and order details on both iOS and Android.
Written by the indexing model from the issue text.
Description
Describe the bug
Currently, there is an inconsistency in the notification system between the Enatega multivendor rider app and the restaurant app. When a rider accepts an order, the restaurant app does not receive any notification indicating that the order has been assigned to a rider. This lack of communication creates a disconnect in the order management process and can lead to confusion and delays in order fulfillment.
To Reproduce
Place an order through the Enatega Multivendor Restaurant App.
Wait for a rider to accept the order for delivery.
Observe that the restaurant does not receive any notification indicating that the order has been assigned to a rider.
Expected behavior
Upon a rider accepting an order for delivery, the restaurant associated with the order should receive a notification informing them that the order has been successfully assigned to a rider. This notification should include relevant details such as the rider's name, estimated time of arrival, and any other pertinent information.
Screenshots
Untitled.video.-.Made.with.Clipchamp.1.mp4
Smartphone (please complete the following information):
Device: IOS & Android.
Additional context
The notification should be sent to the restaurant about the rider has been assigned to their order which they are preparing like customer app sent notification about rider has been assigned.
- 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