Rider information after log in shows previous Rider information in Enatega Multivendor Rider App.

Open

#1,789 opened on Jul 14, 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: Quiet
Tech stack: javascript, react-native
Domain: authentication, mobile

Research direction

No files, tests, or entry points are mentioned. Start by reproducing the login/logout sequence with two rider accounts, then locate the Rider App's authentication and rider-information loading flow. Done means the second rider's information appears after login and no data from the previous rider remains visible.

Written by the indexing model from the issue text.

Description

Issue: Rider Information Persistence After Log-in in Enatega Multivendor Rider App
Description:
There is an issue in the Enatega Multivendor Rider App where the rider's information is persisting and displaying the details of a previously logged-in rider, even after the current rider logs in. This issue can lead to incorrect rider information and potential privacy concerns.

Impact:
Privacy and Data Security: Displaying the information of a previously logged-in rider can raise concerns about data privacy and security.

User Experience: The incorrect display of rider information can confuse and frustrate users.

Steps to Reproduce:
Log in to the Enatega Multivendor Rider App with one rider's credentials.
Log out.
Log in with a different rider's credentials.
Observe that the app displays the information of the previously logged-in rider.
Expected Resolution:
The issue of displaying incorrect rider information after log-in needs to be addressed and resolved. Rider information should accurately reflect the currently logged-in rider to ensure data privacy and provide a smooth user experience.

w1 2023-10-20 at 16 35 46_8d8a5de1
WhatsApp Image 2023-10-20 at 16 35 59_89cbbe39

Activity

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.