[Due for payment 2025-06-25] [Due for payment 2025-06-18] [Due for payment 2025-06-17] Workspace - Extra report named Chat Report in LHN after inviting user to the workspace

[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: 9.1.63-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: N/A
Email or phone of affected tester (no customers): sdjoindsjosdijos@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Create a workspace
3. Go to workspace settings > Overview
4. Click Invite
5. Invite a few users who do not have Expensify account
6. Go to Inbox

Expected Result:

There will be no extra report that is named Chat Report

Actual Result:

There is extra report that is named Chat Report in LHN

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6854732_1749489424899.20250610_011513.mp4

View all open jobs on GitHub

[melvin-bot]

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

[BlameGPT]

Possible culprit PRs for this issue

• Create change report policy and invite submitter #63202: This PR involves inviting users to workspaces and creating workspace chats for them, which aligns with the issue steps of inviting users and seeing an extra 'Chat Report' in LHN.
• Remove a call to getReportNameValuePairs when checking if a thread is disabled #63607: This PR modifies report-related utilities and thread behavior, which could impact report visibility and naming in the LHN after workspace changes.
• fix: Submit button is not shown in More menu for workspace admin #63538: This PR affects workspace chat and report submission flows, which relate to workspace admin interactions and report visibility in chats.

[neil-marcellini]

I suspect that this problem comes from the back end. I'm able to reproduce it on dev with all branches on the latest main version.

2025-06-09_11-10-03.mp4

Now I'll see if I can reproduce it with the production branch of the front end. If it's not reproducible, then we know that it comes from the latest changes on the front end, otherwise, it's probably a backend Web-E issue.

It's not reproducible, so it is a front-end issue.

2025-06-09_11-19-35.mp4

[neil-marcellini]

I suspect this might be involved with the root cause of the problem.

App/src/libs/actions/Policy/Policy.ts

Line 1125 in 8a920ef

report: optimisticReport,

We recently started passing the optimistic report in the report creation data when inviting members to the workspace. I don't really see how the backend uses this though.

reportCreationData on main

{
    "m5@63766.com": {
        "report": {
            "type": "chat",
            "chatType": "policyExpenseChat",
            "isOwnPolicyExpenseChat": false,
            "isPinned": false,
            "lastActorAccountID": 0,
            "lastMessageHtml": "",
            "lastReadTime": "2025-06-09 18:54:47.994",
            "lastVisibleActionCreated": "2025-06-09 18:54:47.994",
            "oldPolicyName": "",
            "ownerAccountID": 514860523,
            "parentReportActionID": "",
            "participants": {
                "67": {
                    "notificationPreference": "always"
                },
                "514860523": {
                    "notificationPreference": "always"
                }
            },
            "policyID": "68ABE0D055F40250",
            "reportID": "4278767499499482",
            "reportName": "Chat Report",
            "stateNum": 0,
            "statusNum": 0,
            "description": "",
            "avatarUrl": ""
        },
        "reportID": "4278767499499482",
        "reportActionID": "7959553601690069024"
    }
}

reportCreationData on production

{
    "m7@63766.com": {
        "reportID": "1499038957703865",
        "reportActionID": "3264151258458714437"
    }
}

Regardless, reverting that PR fixes the problem.

[Julesssss]

I merged the PR and CP'd to staging. @neil-marcellini could you request a retest from QA tomorrow morning? thanks

[mountiny]

https://expensify.slack.com/archives/C9YU7BX5M/p1749559749829159