[Due for payment 2025-04-10] [Due for payment 2025-04-08] [$250] Start chat - Start chat page is broken after refreshing the page

[jponikarchuk]

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.21-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+260302kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Other

Action Performed:

Precondition:

• Browser is Mac Chrome.
• Expensify desktop app is installed.

1. Go to staging.new.expensify.com
2. Create a workspace if there isn't one.
3. Open FAB > Start chat > Chat.
4. Refresh the page.
5. Do not interact with "Open New Expensify" modal first.

Expected Result:

Start chat page will open Chat page.

Actual Result:

Start chat page opens Room page. The tabs disappear. "Description" label input overlaps with the entered text.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6784750_1743110346795.Dvnb8264_1_.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021906720830415317384
• Upwork Job ID: 1906720830415317384
• Last Price Increase: 2025-03-31
• Automatic offers:
• brunovjk | Reviewer | 106732122
• nkdengineer | Contributor | 106732123

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @stephanieelliott

[melvin-bot]

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

[JS00001]

I'm able to repro in staging, looking into it

[JS00001]

This looks like the exact same bug as #59223 (comment), which had its fix reverted, I don't think this is a deploy blocker