Company card - Back button closes assign flow when cardholder list is opened from confirm page

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.2.86-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #78069
Email or phone of affected tester (no customers): applausetester+khcategory20@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Workspace has added a direct feed with card.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Company cards.
3. Click on any unassigned card.
4. Select any user.
5. On confirm page, click Cardholder field.
6. Click RHP back button.

Expected Result:

RHP back button will return to confirm page.

Actual Result:

RHP back button closes assign flow when cardholder list is opened from confirm page.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7035709_1766460353065.10.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #78069

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

Triggered auto assignment to @sonialiap (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.

[github-actions]

👋 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.

[hungvu193]

This is also expected behavior.

Slack discussion is here:

https://expensify.slack.com/archives/C07HPDRELLD/p1766203818259459?thread_ts=1766158986.585989&cid=C07HPDRELLD

and here:

https://expensify.slack.com/archives/C07HPDRELLD/p1766203873103169?thread_ts=1766158986.585989&cid=C07HPDRELLD

We can close. cc @carlosmiceli @dannymcclain