You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Wallet - Default label is only shown after refreshing page when deleting default account #54748
Version Number: 9.0.80-1 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from TestRail:#52322 Email or phone of affected tester (no customers):applausetester+394034@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.0 / Chrome App Component: User Settings
Action Performed:
Precondition:
Account has three personal bank accounts.
Go to staging.new.expensify.com
Go to Account settings > Wallet.
Click on the default bank account.
Click Delete.
Delete the default bank account.
Note that there is no Default badge on the most recently added bank account.
This requires changes on the backend. When a user deletes their default payment method with (DeletePaymentBankAccount) , the frontend doesn’t know which payment method should become the new default. Currently, the backend only returns a payment method marked as isDefault: true after the page is refreshed, which updates userWallet?.walletLinkedAccountID to the new default payment method.
To avoid requiring a page refresh, the backend should update userWallet?.walletLinkedAccountID in the same API (DeletePaymentBankAccount) response when a payment method is deleted, assigning a new default payment method directly.
In summary, when the DeletePaymentBankAccount endpoint is called, the response should include userWallet?.walletLinkedAccountID. This is essential becauseuserWallet?.walletLinkedAccountIDis used to display the default badge on the wallet page.
I think the precondition of Account has three personal bank accounts. is very rare, and this is just a display issue that's resolved upon refreshing. Closing this out.
Activity
melvin-bot commentedon Jan 2, 2025
Triggered auto assignment to @bfitzexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.Shahidullah-Muffakir commentedon Jan 2, 2025
This requires changes on the backend. When a user deletes their default payment method with (DeletePaymentBankAccount) , the frontend doesn’t know which payment method should become the new default. Currently, the backend only returns a payment method marked as
isDefault: trueafter the page is refreshed, which updatesuserWallet?.walletLinkedAccountIDto the new default payment method.To avoid requiring a page refresh, the backend should update
userWallet?.walletLinkedAccountIDin the same API (DeletePaymentBankAccount) response when a payment method is deleted, assigning a new default payment method directly.In summary, when the
DeletePaymentBankAccountendpoint is called, the response should includeuserWallet?.walletLinkedAccountID.This is essential becauseuserWallet?.walletLinkedAccountIDis used to display the default badge on the wallet page.bfitzexpensify commentedon Jan 2, 2025
I think the precondition of
Account has three personal bank accounts.is very rare, and this is just a display issue that's resolved upon refreshing. Closing this out.izarutskaya commentedon Jul 29, 2025
Reproduce in Web using build v9.1.87-0
mac/chrome
Screen.Recording.2025-07-29.at.3.05.46.in.the.afternoon.mp4