Margaret-Petersen / Margaret-Petersen/uber-eats-clone-using-react-native
The rider app is not displaying the map on the screen. bug Something isn't working Enatega Multivendor Rider App good first issue Good for newcomers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
The rider app is not displaying the map on the screen. This prevents riders from viewing their route, navigation, or current location, affecting their ability to complete deliveries efficiently.
To Reproduce
Steps to reproduce the behavior:
Open the rider app
Login with valid credentials
Navigate to the main screen where the map should be displayed
Observe that the map area remains blank or fails to load
Expected behavior
The map should load correctly upon opening the app, showing the rider's current location and the route or nearby areas needed for navigation.
Screenshots
Image
Smartphone (please complete the following information):
Device: Samsung A32
OS: [e.g. Android 13]
Browser: In-app
Version: [App version number]
Additional context
This issue severely impacts the rider's ability to navigate and complete tasks on time. It may be related to GPS permissions, map API integration, or network issues. Prompt resolution is recommended.
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 reproducing the issue in the rider app: log in with valid credentials and open the main screen where the map should appear. Check the map display, current location, and route or nearby-area rendering on the reported Samsung A32 setup; done means the map loads and supports rider navigation.
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
- 25/100