gray-mueller / gray-mueller/food-delivery-clone-app-using-react-native
Notification Discrepancy Between Rider and Restaurant Apps
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
Research direction
Start by tracing the rider order-acceptance flow and the restaurant app's notification handling in the TypeScript/React Native codebase. Reproduce the flow on iOS or Android, then verify that the restaurant receives an assignment notification containing the rider details and expected delivery information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100