Enatega Customer App: Incorrect Layout Displayed – Restaurant Layout Shown for Store Selected from Map View

Open

#2,059 opened on Sep 7, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 65/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Active
Tech stack: javascript, react-native
Domain: mobile-dev

Research direction

Start from the Store screen's map-view marker selection flow and trace which layout opens after a store is tapped. Compare that path with the store-specific layout and its categories, product lists, filters, and UI sections. Done means selecting any store from the map opens the store layout rather than the restaurant layout.

Written by the indexing model from the issue text.

Description

Describe the bug
When the user navigates to the Store screen and views store locations on the map, clicking on any store from the map view opens the restaurant layout instead of the store layout. This causes confusion and misrepresents the content, as store-specific elements (such as categories, filters, and UI sections) are replaced with restaurant-specific components.

Steps to Reproduce:

Open the application and navigate to the Store screen.
Switch to Map View to see the stores on the map.
Tap on any store icon or marker from the map.
Observe the screen that opens after selection.
Expected behavior
Selecting a store from map view should open the correct store layout, showing store-specific categories, product lists, and UI elements (e.g., “Grocery,” “Essentials,” or “Store Info”).

Smartphone (please complete the following information):

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

Labels: Enatega Multivendor Customer App, High Priority, Bug

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

Contributor guide

Open the contributing 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.