lambertf917 / lambertf917/mobile-ordering-solution

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

Open
#59 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Rider App's login and logout entry points and reproduce the sequence with two different rider accounts. Trace where rider information is retained between sessions, then verify that the second login displays only the current rider's information and does not retain the previous rider's details.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authentication, mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.