Payments - Error message appears when making a bank account as a default payment

[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. Go to staging.new.expensify.com and login with Beta account
2. Go to the payments page.
3. Click any existing payment method to set it to default.
4. Click set default

Expected Result:

Success message appears and able to set a payment as a default one

Actual Result:

Failed to set a default method error appears

Error message:

Failed to set a default method error

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• Android
• Desktop App
• Mobile Web

Version Number: 1.1.39.2

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

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

Notes/Photos/Videos: Any additional supporting documentation

Bug5465466_Recording__91.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause

Slack conversation:

Issue was found when execute the PR: #7782

View all open jobs on GitHub

[MelvinBot]

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

[timszot]

@parasharrajat This is related to your PR #7782 that was merged yesterday. Can you take a look here please?

[parasharrajat]

Ok. Thanks. I will debug this. It does not seem related to that change as I also used to get to before that regression on my account. I will update you shortly as this is

[iwiznia]

Reproducible in production?: Yes

Given this, I doubt this is a deploy blocker.

[iwiznia]

@kbecciv I need the user's email to be able to get logs and try to determine if this can be worked on by an contributor or not. Can you give me the email of the user you used and an approximate date and time (including time zone) when the test was done?
Also, do we not include the user's email and other relevant data as part of the issue template??

[kbecciv]

@iwiznia Here is the email user - applausetester++2501mn@applause.expensifail.com and an approximate date and time is 02/22/22 at 5:02 PM EST.

[parasharrajat]

Ok, I tested it. This error is not a regression my PR. #7769 was a regression from the PR which I already solved and it is now on staging.

This seems like a backend error.

[iwiznia]

Thanks @kbecciv!

Logs for the request are here. The error in question is:

Throwing exception with message: '405 Invalid wallet account' from auth/command/SetWalletLinkedAccount.cpp:45

Seems we throw that error when the wallet bank account used is not in OPEN state. I checked and indeed the bank account you are using (id 1432796) is in the SETUP state:

ionatan@db2.sjc:~$ sudo readdb.sh -line "select * from bankaccounts where bankaccountid = 1432796"
       created = 2022-01-25 20:16:56
 bankAccountID = 1432796
     accountID = 11162433
       deleted = 0
 accountNumber = v8:76DAE4A475D1E2B955F559047674FE97
 routingNumber = 011401533
      checking = 0
   addressName = Alberta Bobbeth Charleson
additionalData = REDACTED
   addressCity = true
  addressState = true
    addressZip =
 defaultCredit = 0
         state = 4
  validateCode = REDACTED
     processor =
          type = 1

Now, I am not sure what this means... is the bank account not supposed to be in that state? Are we not supposed to be calling that command in this scenario? I have no idea. Pinging @madmax330 and @MariaHCD as they might have some more context.

[MariaHCD]

I think we don't want to call SetWalletLinkedAccount if the bank account is still in the setup state. cc: @stitesExpensify