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
App directly opens Connect via Plaid flow when adding WS bank after adding personal bank acc #54762
Version Number: 9.0.80-6 Reproducible in staging?: Yes Reproducible in production?: Unable to check, can't add BA on prod If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):applausetester+kh2001014@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.0 / Chrome App Component: Workspace Settings
Action Performed:
Go to staging.new.expensify.com
Log in with a new account.
Create a workspace.
Go to Workspace settings > More features.
Enable Workflows.
Go to Workflows.
Click Connect bank account.
Cilck Update to USD.
Close the RHP after updating to USD. (important)
Go to Account settings > Wallet.
Click Add bank account (Wells Fargo).
Go through add bank account flow.
After adding a personal bank account, go back to Workspace settings > Workflows.
Click Connect bank account.
Expected Result:
RHP will open with Connect via Plaid and Connect manually options.
Actual Result:
RHP directly opens Connect via Plaid setup.
It only shows Connect via Plaid and Connect manually options after quitting the flow and reopening it.
👋 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:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Jan 2, 2025
Triggered auto assignment to @Christinadobrzyn (
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.melvin-bot commentedon Jan 2, 2025
Triggered auto assignment to @marcochavezf (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jan 2, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jan 2, 2025
👋 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:
cead22 commentedon Jan 2, 2025
I thought this was by design. Regardless, I don't think this needs to be a blocker, at least not for web
marcochavezf commentedon Jan 2, 2025
I wasn't able to reproduce it in staging
MelvinBot commentedon Jan 2, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
melvin-bot commentedon Jan 6, 2025
@marcochavezf, @Christinadobrzyn Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
marcochavezf commentedon Jan 6, 2025
I saw a related PR to the bank account flow was reverted, maybe that's why it's not reproducible anymore. I'm going to close it for now