Thread - After leaving a thread, tapping on back button navigates to the thread again.

[nlemma]

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.94-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-272/folder/13177078/41237908/839724415
Email or phone of affected tester (no customers): ibellicotest+1591@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app)
App Component: Other

Action Performed:

1. Open the Expensify app.
2. Open any chat.
3. Send a message.
4. Long tap on the message and select "Reply in thread"
5. Send a message in thread.
6. Tap on thread header and select "Leave"
7. Note that you land on parent conversation.
8. Tap on the back button on the top left corner.
9. Note that you land on thread again instead of navigating to "Inbox"

Expected Result:

After leaving a thread and landing on chat, tapping on back button should navigate to "Inbox"

Actual Result:

After leaving a thread and landing on parent conversation, tapping on the back button, leads to thread again instead of navigating to "Inbox".

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

Bug6916726_1755153133544.Thread.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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