[Due for payment 2026-01-14] [$250] Chat - User has to leave thread twice, to make the "Join Thread" option appear.

[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.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: #75826
Email or phone of affected tester (no customers): ibellicotest+2134@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 11 / Chrome
App Component: Chat Report View

Action Performed:

1. Open the Expensify app.
2. Open any workspace chat.
3. Send a message to chat.
4. Long tap on the message and select "Reply in thread"
5. Send any reply.
6. Return to conversation.
7. Long tap on the message.
8. Note that a "Leave Thread" option appears.
9. Tap on "Leave Thread"
10. Long tap on message again.
11. Note that "Leave Thread" option still appears, despite user having left the thread.
12. Tap on it again.
13. Long tap on message one more time.
14. Note that now, option changed to "Join Thread"

Expected Result:

"Leave Thread" option shouldn´t be available anymore after leaving the thread. Option in context menu should change to "Join Thread" after leaving.

Actual Result:

"Join Thread" option doesn´t appear on context menu until user leaves the thread twice, selecting the "Leave Thread" option.

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

Bug7018167_1764643812310.Leave_twice.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021996234273943456786
• Upwork Job ID: 1996234273943456786
• Last Price Increase: 2025-12-03

Issue Owner

Current Issue Owner: @joekaufmanexpensify

[melvin-bot]

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

[mukhrr]

Checking if BE sends correct data...