Connect Bank - Account number isn't updated and not match that from your other device.

[kbecciv]

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. Log into an account without a Workspace VBA set up (create a new workspace if needed) Used iOS App
2. Go to Workspace settings > Connect bank account
3. Select the Connect manually method to add a bank account
4. Type in incorrect routing and account numbers
5. In a second device (used Web Mac/Chrome), log in to the same account and navigate again to Workspace settings > Connect bank account
6. Enter routing and account numbers that satisfy the requirements (ex 041215032 and 123456), then continue on and complete Step 2 in the flow
7. Refresh the page in first device

Expected Result:

Verify that the Routing number and Account number are now updated to match that from your other device, and the inputs are disabled

Actual Result:

Account number isn't updated and not match that from your other device.
Issue reproduced on Desktop App + iOS App.

Workaround:

Unknown

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.5.4

Reproducible in staging?: Yes

Reproducible in production?: Yes

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: Any additional supporting documentation

Bug6032351_17748__iOS.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~017a366153568a299f
• Upwork Job ID: 1659316205631774720
• Last Price Increase: 2023-05-18

[MelvinBot]

Triggered auto assignment to @puneetlath (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

[MelvinBot]

@puneetlath 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[puneetlath]

Hmm, interesting. I'm not sure whether this is something that we store on the server or locally. Looking into it.

[melvin-bot]

@puneetlath Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

@puneetlath this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[puneetlath]

@kbecciv was this part of an existing testrail flow that you were testing? Right now the way this is built, it doesn't share this info across devices, so I kind of feel like this is more of a feature request than an existing bug.

[kbecciv]

@puneetlath No, this is not part of an existing TR flow, QA team found this issue when executing PR #17748