Chat - App returns to main chat after refreshing Flag as offensive RHP in thread

[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.3.58-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: #85120
Email or phone of affected tester (no customers): sdjsdjnidhhbudshihsuid1@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Chat Report View

Action Performed:

Precondition:

• User has received a message from another user.

1. Go to staging.new.expensify.com
2. Open 1:1 DM with received message.
3. Right click on the message > Reply in thread.
4. Right click on the parent message in thread >  Flag as offensive.
5. Refresh the page.

Expected Result:

App will stay in thread after refreshing Flag as offensive RHP in thread.

Actual Result:

App returns to main chat after refreshing Flag as offensive RHP in thread.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7126615_1775816763813.4.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @collectioneur

[melvin-bot]

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

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