Margaret-Petersen / Margaret-Petersen/uber-eats-clone-android

Enatega Customer Applioction : Whenever an order is placed, the estimated delivery time always shows 0–5 minutes, regardless of the prep time set in the restaurant app.

Open
#1,002 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
When an order is placed, the estimated delivery time always displays as 0–5 minutes, regardless of the actual prep time set by the restaurant. This causes confusion for users, as it does not reflect the realistic time required for food preparation and delivery.

To Reproduce
Steps to reproduce the behavior:

Go to 'Enatega Customer Application'
Place any order.
Now wait until your order is received by the restaurant, see error that on the screen it always showing estimated delivery time 0-5 minutes instead of the food preparing time selected by the restaurant.
Expected behavior
The estimated delivery time should factor in the restaurant's prep time and provide a realistic delivery window, such as 15–20 minutes if that's the restaurant's standard preparation time.

Screenshots

WhatsApp.Video.2025-01-17.at.4.06.02.PM.mp4
Image

Smartphone (please complete the following information):

Device: [e.g. Infinix hot 50]
OS: [e.g. Android]
Browser [e.g. Application]
Version [e.g. 14]
Activity

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Enatega Customer Application's order status and estimated-delivery display, then trace how the restaurant's preparation time reaches that screen. Reproduce an order with a nonzero restaurant prep time and verify the displayed delivery window reflects it instead of always showing 0–5 minutes; no specific file or test is named.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, javascript
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.