Unexpected Logout Triggered by Clicking Above Logout Button Boundary

Open

#1,676 opened on Jan 8, 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: 48/100

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

Research direction

Start by reproducing the logout interaction on the iOS and Android logout screen, then locate the logout button implementation. Check why taps above the button are included in its touch area. Done means logout occurs only for taps within the button boundary, verified on both platforms.

Written by the indexing model from the issue text.

Description

Description:
When using the Enatega Multivendor Rider App, users have reported an unexpected behavior when attempting to log out. Upon clicking above the logout button, even outside of its designated boundary, the app still proceeds to log the user out. This behavior is inconsistent with the expected functionality, where the logout action should only be triggered when directly clicking within the button area.

To Reproduce

Open the Enatega Multivendor Rider App.
Navigate to the screen where the logout button is located.
Position the cursor slightly above the designated boundary of the logout button.
Click the mouse or tap the screen.
Expected behavior
The logout action should only be triggered when clicking directly within the logout button boundary.
Actual Behavior:

Clicking above the logout button, even outside its designated boundary, results in the app logging the user out, which is unintended behavior.

Screenshots
https://github.com/ninjas-code-official/food-delivery-multivendor/assets/153413752/99dcd814-c38a-4daa-b1ce-75fe4dd85d68

Smartphone (please complete the following information):
IOS & Android

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.