marthaegrimaldi / marthaegrimaldi/meal-ordering-app-using-react-native
Rider Not Notified When Restaurant Accepts Order
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When a restaurant accepts an order placed by a customer through the Enatega multivendor application, the associated riders are not receiving notifications informing them that an order has been accepted.
To Reproduce
Place an order as a customer through the Enatega multivendor application.
Wait for the restaurant to accept the order.
Check the rider app for notifications regarding newly accepted orders.
Note that no notification is received by the rider app
Expected behavior
When a restaurant accepts an order placed by a customer through the Enatega multivendor application, the associated riders should promptly receive a notification informing them of the new order.
Screenshots
screen-20240311-110218.mp4
Smartphone (please complete the following information):
Device: IOS & Android.
Additional context
for more context the notification in the screen recording is generated for customer app not rider app.
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.
Research direction
Start by tracing the order-acceptance notification flow between the restaurant, customer, and rider apps, using the rider app notification behavior and the customer-app notification shown in the recording as entry points. Confirm where an accepted order is dispatched and how rider notifications are handled. Done means riders on both iOS and Android receive a notification when the restaurant accepts an order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100