Repository navigation
[Due for payment 2026-04-23] Chat - App returns to main chat after refreshing Flag as offensive RHP in thread #87602
Description
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.
- Go to staging.new.expensify.com
- Open 1:1 DM with received message.
- Right click on the message > Reply in thread.
- Right click on the parent message in thread > Flag as offensive.
- 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
Issue Owner
Current Issue Owner: @huultMetadata
Metadata
Type
Projects
- Status
Activity
melvin-bot commentedon Apr 10, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #85120
melvin-bot commentedon Apr 10, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Apr 10, 2026
👋 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:
OSBotify commentedon Apr 10, 2026
Investigation Summary: Classification: Frontend bug. Causing PR: #85120 - Implement parameters handling in dynamic routes by @collectioneur (High confidence). Recommendation: REVERT. PR 85120 migrated FLAG_COMMENT from a legacy static route with backTo param to the dynamic route system. The regression occurs when refreshing the page while the Flag as offensive RHP is open from within a thread view - the app navigates to main chat instead of staying in the thread. Assigned: @collectioneur (PR author), @WojtekBoman @huult @mjasikowski (approving reviewers). Labels: No label changes made. DeployBlockerCash is correctly set; this is a Frontend/App bug requiring a fix or revert of an App PR. Evidence: Issue body and melvin-bot both point to PR 85120 as the causing PR. Bug is staging-only (9.3.58-0). PR 85120 is in the StagingDeployCash checklist. Root cause: SCREENS.DYNAMIC_FLAG_COMMENT is not registered in any RHP_TO_* relation map; getAdaptedStateFromPath falls through to dynamic route code path in getMatchingFullScreenRoute and does not correctly restore thread context after refresh. Key files: src/ROUTES.ts, src/libs/Navigation/helpers/getStateFromPath.ts, src/libs/Navigation/helpers/getAdaptedStateFromPath.ts, src/pages/inbox/report/ContextMenu/ContextMenuActions.tsx
7 remaining items
[-]Chat - App returns to main chat after refreshing Flag as offensive RHP in thread[/-][+][Due for payment 2026-04-23] Chat - App returns to main chat after refreshing Flag as offensive RHP in thread[/+]melvin-bot commentedon Apr 16, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.59-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-04-23. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 16, 2026
@huult The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
huult commentedon Apr 16, 2026
Fixed price project, no need for payment.
melvin-bot commentedon Apr 21, 2026
@huult Huh... This is 4 days overdue. Who can take care of this?
huult commentedon Apr 22, 2026
This PR has been released to production, so I think we can close this.