[Due for payment 2025-07-30] [Due for payment 2025-07-28] Android - Reports - Context menu does not open on long press on expense row

[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.1.83-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp #65500
Email or phone of affected tester (no customers): applausetester+150701kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy Z Fold 4 / Android
App Component: Search

Action Performed:

Precondition:

• Log in with an account that has completed onboarding.

1. Launch Expensify app.
2. Create a new workspace.
3. Go to Inbox.
4. Go to workspace chat.
5. Submit an expense.
6. Go to Reports tab.
7. Long press on expense row.
   → Context menu opens.
8. Go to Workspaces > Workspace settings.
9. Tap on the workspace chat.
10. Tap app back button.
11. Go to Reports.
12. Long press on expense row.

Expected Result:

Context menu opens.

Actual Result:

Context menu no longer opens.

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

Bug6891224_1752818561231.Screen_Recording_20250718_135903_Expensify.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @stephanieelliott

[melvin-bot]

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

[rushatgabhane]

@BlameGPT please find the cause