[Due for payment 2025-12-11] Wallet - Clicking the assigned Expensify card row opens both RHP and 3-dot menu

[jponikarchuk]

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: v9.2.67-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: Exploratory #60290
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Device used: Mac 15.4.1 Safari, iPhone 13 Safari, Hybrid
App Component: User Settings

Action Performed:

1. Navigate to https://staging.new.expensify.com
2. Log in with an Expensifail account
3. Create a workspace and assign an Expensify card
4. Navigate to Wallet
5. Click the 3-dot menu
6. Click the assigned card row

Expected Result:

Clicking the assigned card row should open only RHP with card details, while clicking the 3-dot menu opens a pop-up menu

Actual Result:

Clicking the assigned card row opens both RHP and 3-dot menu
In production, the 3-dot menu is missing

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @strepanier03

[melvin-bot]

Triggered auto assignment to @strepanier03 (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]

Triggered auto assignment to @grgia (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

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

[koko57]

probably from my PR, looking 👀

[grgia]

@koko57 which PR?