Android - VBA - App crashed when initiating VBA flow 2nd time after disconnecting already added one

[kavimuru]

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

---

Action Performed:

1. Launch the app
2. Log in with expensifail account
3. Go to any Workspace and select Connect bank account
4. Add bank account following VBA flow
5. After bank is validated - tap disconnect bank account
6. Go to any Workspace and select Connect bank account
7. Continue VBA flow
8. After entering chase bank credentials select saving accounts

Expected Result:

Able to continue and connected with bank account

Actual Result:

App crashed when initiating VBA flow 2nd time after disconnecting already added one

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Android

Version Number: 1.1.14.0

Reproducible in staging?: Yes
Reproducible in production?: Unable check in production with test credentials

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos:

Bug5313612_Screen_Recording_20211105-035529_New_Expensify.mp4

Bug5313612_VBA_crashed.txt

Expensify/Expensify Issue URL:

Issue reported by: Applause
Slack conversation:

View all open jobs on GitHub

[OSBotify]

👋 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.

[MelvinBot]

Triggered auto assignment to @NikkiWines (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[NikkiWines]

I'm able to reproduce something similar on web where I just get endless loading spinners when trying to add the bank account again.

@kavimuru does this issue also occur on iOS for you guys? Or is it only reproducible on Android?

[NikkiWines]

Figured out the root cause I believe - looking into a fix now

[isagoico]

@NikkiWines Forgot to post the iOS result here, my apologies. The issue is also reproducible on iOS.