[$250] mWeb -Error page when open #exfy-roadmap while #new-expensify-feedback is open

[lanitochka17]

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: 1.4.82-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4622123&group_by=cases:section_id&group_id=229066&group_order=asc
Email or phone of affected tester (no customers): gocemate+a233@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Logout of New Expensify if logged in
2. Navigate to the following link - https://staging.new.expensify.com/r/6776919265133947
   (#new-expensify-feedback)
3. While #new-expensify-feedback is open navigate to the following link - https://staging.new.expensify.com/r/868417741568295
   (#exfy-roadmap)

Expected Result:

#exfy-roadmap room should open and chat history should be visible

Actual Result:

Error page appears when navigate to #exfy-roadmap link while #new-expensify-feedback is open

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6510717_1718191721627.Recording__3174.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~017e4f9542b1cde2bc
• Upwork Job ID: 1800937045717141030
• Last Price Increase: 2024-07-17

[melvin-bot]

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

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

[lanitochka17]

@youssef-lr FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[tsa321]

Possible offending PR: #43090

[tsa321]

or maybe #43159