[$250] Chat - Compose Box Remains Visible on Archived Report After Workspace Deletion

[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.97-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #68269
Email or phone of affected tester (no customers): qaooxx+351@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Open the app
2. Create a workspace
3. Create a distance expense
4. Delete the workspace
5. Open the archived report

Expected Result:

Compose box should not appear on an archived report

Actual Result:

Compose box remains visible even though the report is archived

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

Bug6921433_1755637638408.1_58_PM_2025-08-19.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021960547763317723557
• Upwork Job ID: 1960547763317723557
• Last Price Increase: 2025-08-27

Issue Owner

Current Issue Owner: @Ollyws

[melvin-bot]

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

[Eskalifer1]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Chat - Compose Box Remains Visible on Archived Report After Workspace Deletion

What is the root cause of that problem?

Here is the line where we check whether composer can be displayed:

App/src/pages/home/report/ReportFooter.tsx

Line 119 in c88901d

const shouldHideComposer = !canPerformWriteAction || isBlockedFromChat;

But here we don't check whether the expense is archived, only isArchivedNonExpenseReport inside canUserPerformWriteAction

What changes do you think we should make in order to solve the problem?

We need to add more checks to see if the report is archived:
const shouldHideComposer = !canPerformWriteAction || isBlockedFromChat || isReportArchived;

PS: If necessary, we can also add a check to see if it is isExpenseReport(report) || isExpenseRequest(report) or isMoneyRequestReport or any other that can be used in this case. What function to use we can discuss during PR stage

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N/A

What alternative solutions did you explore? (Optional)

We can move this check to canUserPerformWriteAction if needed
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[lorretheboy]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Chat - Compose Box Remains Visible on Archived Report After Workspace Deletion

What is the root cause of that problem?

The problem is in the canUserPerformWriteAction function. Currently, it only blocks write actions for archived non-expense reports, but it should block write actions for all archived reports.

App/src/libs/ReportUtils.ts

Line 9020 in 9bec0c0

function canUserPerformWriteAction(report: OnyxEntry<Report>) {

What changes do you think we should make in order to solve the problem?

Update to return early if it is archived like existing pattern in codebase (Archived reports should be archived, cannot having errors, actions on them)

    const isArchived = isReportArchived ?? !!reportNameValuePairs?.private_isArchived;

    // Prevent write actions on any archived report
    if (isArchived) {
        return false;
    }

    return (
        isEmptyObject(reportErrors) &&
        report &&
        isAllowedToComment(report) &&
        !isAnonymousUser &&
        canWriteInReport(report)
    );

App/src/libs/ReportUtils.ts

Lines 9031 to 9039 in 9bec0c0

	return (
	!isArchivedNonExpenseReport(report, !!reportNameValuePairs?.private_isArchived) &&
	isEmptyObject(reportErrors) &&
	report &&
	isAllowedToComment(report) &&
	!isAnonymousUser &&
	canWriteInReport(report)
	);
	}

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

NA

What alternative solutions did you explore? (Optional)

NA

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[melvin-bot]

@johncschuster Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@johncschuster Still overdue 6 days?! Let's take care of this!

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021960547763317723557