Android - Connect bank account - App is crashed after selecting Save & Continue button

[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. Open the test app and log in with a applause.expensifail account (that does not have any bank account already added)
2. Enable staging Web secure server in Account Preferences
3. Navigate to Workspace editor page
4. Select Connect bank account
5. Select Connect online with Plaid
6. Select Wells Fargo bank
7. Enter the test credentials
8. Choose the savings account "Plaid Saving11122XXXXXX111"
9. Select Save & Continue button

Expected Result:

Able to add bank account successfully.

Actual Result:

App is crashed after selecting Save & Continue button. Unable to add a bank account.

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Android

Version Number: 1.1.43.1

Reproducible in staging?: Yes

Reproducible in production?: No (unable to check VBA flow in Prod, last Regression didn't have issue)

Email or phone of affected tester (no customers): applausetester+ab2@applause.expensifail.com

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

Notes/Photos/Videos: Any additional supporting documentation

Bug5493022_screen-20220316-125906.mp4

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 @bondydaa (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[thesahindia]

Also reproducible on Add debit card page.

[roryabraham]

Going to try to take a crack at this issue

[nickmurray47]

@roryabraham let me know if you need any help digging, too, I'm familiar with how our Plaid flow is supposed to work

[roryabraham]

Yeah @nickmurray47 more eyes would be great to get this resolved as fast as possible!

[nickmurray47]

FYI I don't have a physical Android device, so not sure if it's possible for me to test Android staging myself?

[roryabraham]

#7813 seems to be the most likely culprit. Going to try investigating that first

[roryabraham]

FYI I don't have a physical Android device, so not sure if it's possible for me to test Android staging myself?

I don't either, going to see if we can reproduce on dev

[roryabraham]

You can make the dev app communicate with staging or production APIs too if you want, though I'm going to just use the VM to start.

[nickmurray47]

Let me know if you're able to reproduce @roryabraham.

Something to note looking at the tester's screencap is that they appear to be in Plaid's sandbox environment still? logs here

Wells Fargo is one of the bank connections that uses Plaid's upgraded sign-in route where we actually take you to the Wells Fargo site and then bring you back to Expensify. From the tester's video, it looks like they just went through the old sign-in route. If you try to use Wells Fargo through staging.new.expensify.com you can see what the flow is supposed to look like on prod.

[roryabraham]

Saw this after PlaidLink was completed:

[roryabraham]

Yep, as expected found the cause:

Going to have a fix up for CP momentarily. Crashlytics was very useful in this case.