hector-jewell / hector-jewell/uber-eats-clone-using-react-native
Google Map Not Responsive or Displaying Properly During Order Pickup and Delivery
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description:
When food is being picked up from the restaurant or delivered to the customer, the Google Map is not responsive or being displayed properly. This issue occurs on both Android and iPhone devices. On Android, the map is unresponsive, while on iPhone, it is responsive but not displayed correctly.
Steps to Reproduce:
1-Open the Enatega Rider App on an Android or iPhone device.
2-Accept a food delivery order.
3-Navigate to the pickup location and observe the Google Map.
4-Pick up the order and proceed to the delivery location.
5-Observe the Google Map during both pickup and delivery stages.
Expected Behavior:
The Google Map should be responsive and displayed correctly on both Android and iPhone devices during the order pickup and delivery stages.
Actual Behavior:
1-On Android devices, the Google Map is unresponsive.
2-On iPhone devices, the Google Map is responsive but not displayed properly.
Screenshots:
Android:
(https://github.com/user-attachments/assets/f56c3f6d-80ae-4d19-aef6-60c8db40093d)
iPhone:
(https://github.com/user-attachments/assets/41563e6c-bf6f-4274-adc1-6d6456719b6a)
Additional Information:
Please investigate the cause of the map display issues on both Android and iPhone devices and provide a fix to ensure the Google Map is responsive and displayed correctly during the order pickup and delivery stages.
Contributor guide
Research direction
Begin in the Enatega Rider App's map flow during pickup and delivery, reproducing the reported behavior on Android and iPhone using the provided screenshots as reference. No file or test is named, so first locate the relevant map entry point; done means the map responds and displays correctly on both platforms.
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
- Needs clarification
- Newbie friendliness
- 35/100