Connect Bank Account - User can't add Fidelity bank because of connectivity error message

[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 the New expensify app
2. Sign into a valid account
3. Tap on Profile > Workspace > Connect to bank
4. Select "Plaid" and select Fidelity Bank

Expected Result:

User expects to be able to continue with the VBA flow

Actual Result:

User receives an error message and can not proceed

Workaround:

unknown

Platform:

Where is this issue occurring?

• iOS
• Android

Version Number: 1.12.13-3
Reproducible in staging?: y
Reproducible in production?: can't check
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: https://user-images.githubusercontent.com/43996225/195569592-2f097a1f-51f2-402f-b663-9adeb59d5951.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

View all open jobs on GitHub

[melvin-bot]

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

[PauloGasparSv]

Taking a look at this in the afternoon since right now Fidelity connection is unavailable:

[kbecciv]

@PauloGasparSv There is another error message in Web when using "Plaid" option, please let me know if we need to create a new GH issue for that.

Bug5775553_User_receives_error_message_in_Plaid_flow.1.mp4

[PauloGasparSv]

No need @kbecciv, this new error replaced the old right?
Sorry for taking so long to work on this, it's the very next item on my todo list : )

[kavimuru]

@PauloGasparSv We are still seeing the same error message in iOS though. But in the web, we are seeing the above error in step 4 of 5 as in the video.

[PauloGasparSv]

No way, there is another window of time where the service is unavailable! 🤦🤦🤦
I'll only have time to look at it on Monday because of that, sorry!

So from 9AM to 11AM ET and from 3PM to 5PM ET the service is down.
Which means I have 11AM to 3PM ET (12PM to 16PM BRT) to debug this on Monday

[PauloGasparSv]

Taking a look at this today during the timeframe the service is up (right after lunch)

[PauloGasparSv]

@kavimuru @kbecciv I just tried again on desktop following this comment+video!

I got the same error message.
Then tried again with the SSN as 3333 as specified in this S.O. and it worked!

@kavimuru @kbecciv Can you test this again with that test user but with the 3333 SSN and see if works for you too?

[kbecciv]

@PauloGasparSv
Re-testing, update you shortly.

[kbecciv]

@PauloGasparSv I was able to add the VBA, but faced the error message #11796 (comment) - only worked around using back button and click continue again.
Please attached the video, tested on Windows/Chrome

Recording.1463.mp4

[PauloGasparSv]

Oh! Maybe it only worked for me because of that too but I thought the SSN fixed it!
Testing it again here

[PauloGasparSv]

Replicated here, the SSN was not the issue.
For some reason the first attempt to save the Fidelity connection fails but if you go back and try again it works.

Investigating the issue here!

[PauloGasparSv]

Will take some more time to work on this. Can't debug web-secure to understand the error due to the Php8.1 upgrade that is happening right now, Web-Secure is still not working with the updated version.

Will debug this again tomorrow since the timeframe of the Fidelity API's is closing by anyway!

[PauloGasparSv]

Getting a blank screen now instead of the error, debugging it locally (just finished setting web-scure up with php 8.1)! Not sure what the cause is yet.

[PauloGasparSv]

I'm changing this to weekly since I'm taking little longer than expected to solve this and it isn't affecting a prod customer yet!

[PauloGasparSv]

Tested once again but the connection worked at first try this time and did not give me that unvailable timeframe error:

Then I removed the bankAccount from my user and tried connecting it to the workspace again and got this error I'm investigating:

That error's UUID is 6893fbdb-755b-4c72-85fc-3fa5dab0e705 but sadly there are three different places that return the same uuid. Not sure if that's correct.

[PauloGasparSv]

@kbecciv Do you mind testing this again? Other than staging iOS and Android the Fidelity connection should be working on all the other platforms.

I got the errors above when the service went down like it does daily but it to work locally on Web, locally on mobile and on staging Web!

This got super confusing so I'd appreciate another round of tests : p

[kbecciv]

@PauloGasparSv I will test the Web and mWeb shortly, will update you with videos.

[kbecciv]

@PauloGasparSv Just checked with recent build 1.2.20 and got crashed on both environments.

Screen_Recording_20221026-210902_Chrome.mp4

Recording.1527.mp4

[PauloGasparSv]

What!!!!! Thks @kbecciv, I got that error once from all the 10 or attempts I did yesterday.
I'll try digging into this some more and reach for help if I can't find anything

[melvin-bot]

@davidcardoza, @techievivek Whoops! This issue is 2 days overdue. Let's get this updated quick!

[techievivek]

I did test this couple of times on staging but I wasn't able to reproduce this even once.

[techievivek]

Looking more into it using Logs from here https://www.expensify.com/_devportal/tools/logSearch/#sort=asc&size=10000&query=blob%3A%22An%20unexpected%20error%20occurred%20while%20trying%20to%20update%20your%20bank%20account%22%20AND%20timestamp%3A%5B2022-11-01T00%3A00%20TO%202022-11-15T23%3A59%5D
Will update shortly.

[techievivek]

The error is shown for 3 commands. ConnectBankAccountWithPlaid, UpdateCompanyInformationForBankAccount, UpdatePersonalInformationForBankAccount. And it has to do with the bankAccountID param passed. From newDot when we add a new VBBA for the first two commands it doesn't expect us to pass the bank account but in the instances where errors are thrown it's mostly a bankAccountID is passed and I would assume that bankAccountID doesn't belong to the user and it throws an error when it doesn't find it in the list of bank accounts that user has. In the case of UpdatePersonalInformationForBankAccount it throws an error when bankAccountID = 0 so in this case I would guess the pusher hasn't sent the newly created bankAccountID to the user. I will dig into some more during the later part of the day.

[techievivek]

I wasn't able to look into it because my xdebug was broken, just fixed it by rebuilding the VM.

[melvin-bot]

@davidcardoza, @techievivek Whoops! This issue is 2 days overdue. Let's get this updated quick!

[davidcardoza]

@techievivek any update here?

[techievivek]

Sorry, I was ooo. I will look into it today and give an update.

[techievivek]

@kbecciv I did have another look into it and tested it again on staging, but I can't seem to reproduce it. Can you try reproducing this one more time because even logs are no longer available? Thanks

[kbecciv]

Issue is reproduced in build 1.2.31.8

Screen_Recording_20221125-151731_New.Expensify.mp4

[techievivek]

@kbecciv That seems like standard connectivity down info and doesn't look like an error from our end. I tested this myself on staging seems to work fine now.

Screen.Recording.2022-11-28.at.10.19.45.AM.mov

[techievivek]

I tried this with a new account, and I was able to add the account without any issues. @kbecciv, what you have shared is not something we can fix from our end. If you can reproduce some error while adding the bank account, that is something concerning for us. If there are no issues while adding the bank account(unrelated to Plaid showing something from their end), things seem to work fine.

@davidcardoza Any thoughts here?

[davidcardoza]

I tried reproducing myself and couldn't come up with an error. I am going to close this out. Please reopen if the issue is reproducible Expensify error and not one stemming from Plaid.

[mvtglobally]

Guys This issue is a pain. We are really blocked on Native aps.
@techievivek @davidcardoza Did you use real IOS/Android devices to validate this?

[mvtglobally]

check this tread as well https://expensify.slack.com/archives/C01GTK53T8Q/p1666811104732769

[davidcardoza]

Tested on iOS. I am still not reproducing

RPReplay_Final1670278015.MP4