Scroll Function Not Working Properly on Store/restaurant Page in Enatega Customer App

Open

#1,075 opened on Sep 5, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 30/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: javascript, react-native
Domain: mobile

Research direction

No source file or test is identified. Reproduce the issue on the Enatega customer app using a Samsung A15 on Android, then trace the store page's scrolling and layout behavior, including the reported nested-scroll or heavy-content possibilities; done means smooth, continuous browsing through store items without lag or getting stuck.

Written by the indexing model from the issue text.

Description

Describe the bug
On the store page of the Enatega customer app, the scrolling function is not behaving as expected. Users experience difficulty scrolling through the content — it either lags, gets stuck, or doesn’t respond smoothly, making it hard to browse through items or sections.

To Reproduce
Steps to reproduce the behavior:

Open the Enatega customer app
Navigate to any store page
Attempt to scroll down through the store items or content
Observe that the scrolling is unresponsive, jerky, or gets stuck
Expected behavior
Users should be able to scroll smoothly and continuously through all the content on the store page without any lag or interruption.

Screenshots

XRecorder_20250617_02.mp4
Smartphone (please complete the following information):

Device: Samsung A15

OS: Android

App Version: [insert version if known]

Additional context
This could be related to layout rendering issues, nested scroll views, or performance bottlenecks caused by heavy content. It directly affects the user experience while browsing stores in the app.

Dominant language: JavaScript
Stars: 2
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.