[HOLD] When pressing back from Step 2 (Connect Bank Manually), it navigate to Connect Bank Account page.

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Open workspace => connect bank account manually, enter valid information for first 3 steps, close the page.
2. Go to Workspace => connect bank account manually again => Continue with setup => Press back to go back to Step 2, press Back again.
3. Notice that when you are at step 2 and press back, it navigate to Connect Bank Account page.

Expected Result:

It should navigate to step 1, when user press back at step 2.

##Actual Result:
When you are at step 2 and press back, it navigate to Connect Bank Account page.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

• MacOS / Chrome / Safari

Version Number: v1.2.67-6
Reproducible in staging?: Y
Reproducible in production?: Could not check
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Screen.Recording.2023-02-08.at.15.16.02.mov

Recording.1472.mp4

Expensify/Expensify Issue URL:
Issue reported by: @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1675844399748989
View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @miljakljajic (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[miljakljajic]

I'm not able to reproduce this: it takes me back to step 1, as expected:

[MelvinBot]

@miljakljajic Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[miljakljajic]

bumped on the slack thread

[miljakljajic]

Holding for this: #11768

[miljakljajic]

Still holding!

[miljakljajic]

Holding

[miljakljajic]

Holding

[miljakljajic]

Holding

[miljakljajic]

Holding

[miljakljajic]

Still holding!

[miljakljajic]

Still held

[hungvu193]

Seems this issue is fixed with navigation reboot, am I eligible for reporting bonus? @miljakljajic

[melvin-bot]

Looks like something related to react-navigation may have been mentioned in this issue discussion.

As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our DeprecatedCustomActions.js files should not be accepted.

Feel free to drop a note in #expensify-open-source with any questions.