Enatega Customer App: Updating Name Redirects User to Discovery Screen Instead of Account Screen

Open Beginner friendly
#2,596 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
javascript
Domain
mobile

Research direction

Start by reproducing the name update flow on the Android customer app from Account settings, then trace the navigation triggered after saving the name. Done means a successful update leaves the user on the Account screen instead of redirecting to Discovery.

Written by the indexing model from the issue text.

Description

Describe the bug
When a user updates their name in the account settings, the app redirects them back to the discovery screen instead of staying on the account screen.

To Reproduce
Steps to reproduce the behavior:

Open the app.
Go to Account screen.
Edit and update the name.
Observe the screen navigation after saving.
The app redirects to the discovery screen after updating the name.
Expected behavior
The user should remain on the Account screen after successfully updating their name.

Smartphone (please complete the following information):

Device: [Infinix]
OS: [Android]
Browser [app]

Labels: Enatega Multivendor Customer App, Bug

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

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.

More from gray-mueller/food-ordering-app-using-python

All issues in gray-mueller/food-ordering-app-using-python

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.