[$500] Bank account - Beneficial owner step is restarted after coming back online

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: v1.4.41-2
Reproducible in staging?: Y
Reproducible in production?: N
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
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

Pre-requisite: the user must be logged in and have created a workspace.

1. Go to Workspace > Bank account.
2. Initiate the add BA flow until you reach the Beneficial owner step.
3. Try to add an additional beneficial owner.
4. In the middle of the process (on the SSN, page for example) disable the internet connection.
5. Verify the bottom banner for offline status appears.
6. Enable the internet connection.
7. Wait until it loads.

Expected Result:

The same page when the user was offline should be displayed when coming back online.

Actual Result:

The beneficial owner step is restarted after coming back online.

note: Also, if the user enters the beneficial owner's data without saving it and goes back, when the page is reopened, the data entered previously is not saved.

Workaround:

unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6378788_1707870302997.Dtxx1604_1_.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0112558f96658aedef
• Upwork Job ID: 1757590010053427200
• Last Price Increase: 2024-02-14

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0112558f96658aedef

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov (External)

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Auto-assign attempt failed, all eligible assignees are OOO.

[Beamanator]

Possibly related to #34498, noted in slack here: https://expensify.slack.com/archives/C01GTK53T8Q/p1707899310534299?thread_ts=1707829954.739589&cid=C01GTK53T8Q

[mountiny]

@anmurali posted here https://expensify.slack.com/archives/C07J32337/p1707880864491329 I agree this is not bug, we save the details in backend once the step is saved so in this case it makes sense its missing after going back

I think we can close this