Location Icons Are Cut Off on Customer App
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript, react-native
Research direction
Start by reproducing the issue in the Enatega customer app on a Samsung A15 running Android 14, beginning at the “Welcome to Enatega” page. Inspect the location icons and map rendering to determine whether clipping, static display, distortion, or failure to render is occurring; done means the icons are fully visible and aligned and the map loads interactively.
Written by the indexing model from the issue text.
Description
Describe the bug
In the customer app, the location icons (e.g., those shown for store delivery info or address sections) appear to be cut off or partially hidden. This affects the visual clarity of the UI and makes the design appear broken or misaligned. I issue will be reproduce when user first time install the application.
To Reproduce
Steps to reproduce the behavior:
Open the Enatega customer app
Wait for the app to load the "Welcome to Enatega" page
Observe the map displayed on this screen
Verify whether the map loads properly and is interactive, or if it appears as a static image, distorted, or fails to render correctly
Expected behavior
All icons, including location icons, should be fully visible and properly aligned with adequate padding/margin to prevent clipping.
Smartphone (please complete the following information):
Device: Samsung A15
OS: Android 14
App Version: [insert if known]
Additional context
This is likely a UI rendering issue caused by insufficient padding, margin, or incorrect icon scaling. Fixing this will improve the visual consistency and usability of the app.
Labels: Enatega Multivendor Customer App, Bug, Good First Issue
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from raymondjames090/uber-eats-app-clone-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2069 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2003 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raymondjames090/uber-eats-app-clone-using-react-native#2002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#1979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
raymondjames090/uber-eats-app-clone-using-react-native#1978 ·
All issues in raymondjames090/uber-eats-app-clone-using-react-native
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100