[Due for payment 2026-06-03] [Due for payment 2026-05-26] [Due for payment 2026-05-26] Unable to edit sent message in narrow screen when room posting permission is disabled

[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.3.75-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #90516
Email or phone of affected tester (no customers): sdjoinsjdosjiondsoj2@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:

• Admin creates a room and invites member to the room.

1. Go to staging.new.expensify.com
2. [Member] Send a message in the invited room.
3. [Admin] Click on the room header > Settings > Who can post.
4. [Admin] Select Admins only.
5. [Member] Wait for "Only admins can send messages in this room" to show up in the room.
6. [Member] Resize screen to narrow on web. Skip this step on mweb, Android and iOS.
7. [Member] Right click on the message from Step 2 > Edit comment.

Expected Result:

Member can edit sent message in narrow screen when room posting permission is disabled.

Actual Result:

Member cannot edit sent message in narrow screen when room posting permission is disabled.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @hungvu193

[melvin-bot]

@mountiny recently merged #90516, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #90516 - "Allow editing messages in Composer on narrow screens V2" by @chrispader (High confidence)
Related Issues: #64085, #90512, #90444, #90492, #90435, #90433, #90431, #90430

Recommendation: REVERT

PR #90516 introduced narrow-screen editing that routes the edit flow through the bottom composer, but non-admin members in admins-only rooms never have the bottom composer rendered — they see only an admins-only banner. Reverting this PR restores the previous inline editing behavior, which worked correctly for this case.

Assigned: @chrispader (PR author), @hungvu193, @mountiny (approving reviewers)
Labels: DeployBlockerCash kept (Frontend bug — App PR is the cause). No label changes made.

Detailed Analysis

Evidence

• The melvin-bot comment on the issue directly points to PR Allow editing messages in Composer on narrow screens V2 #90516 as the recently merged PR.
• PR Allow editing messages in Composer on narrow screens V2 #90516 is listed in the StagingDeployCash as merged for this staging version (9.3.75-1).
• The bug is reproducible on staging only (not production), meaning it was introduced by one of the PRs in this staging cycle.
• The PR explicitly changes narrow-screen message editing to use the bottom composer instead of inline editing within the message list.

Verification

• ReportFooter.tsx is the affected file. When isAdminsOnlyPostingRoom returns true and the user is not a policy admin, shouldHideComposer is true and the ReportActionCompose component (bottom composer) is never rendered. Instead, an admins-only banner is shown.
• canUserPerformWriteAction calls isAllowedToComment, which calls isAdminsOnlyPostingRoom (checks writeCapability === CONST.REPORT.WRITE_CAPABILITIES.ADMINS). For non-admin members this returns false, causing the composer to be hidden.
• PR Allow editing messages in Composer on narrow screens V2 #90516 modifies ReportActionCompose/, ReportFooter.tsx, ReportActionsList.tsx, ReportActionItemMessageEdit.tsx, and introduces useEditComposerToggle.ts and useActiveDraftReportAction.ts — all directly related to the editing flow in narrow vs. wide screens.
• The PR's ComposerProvider.tsx sets isEditingInComposer = shouldUseNarrowLayout && editingState !== 'off', routing all narrow-screen edits through the bottom composer.

Root Cause

Before PR #90516, message editing on narrow screens used inline editing within the message list (the ReportActionItemMessageEdit component). This worked regardless of the room's posting permissions because editing an existing message does not require the bottom composer.

PR #90516 changed narrow-screen editing to use the bottom composer instead. However, for non-admin members in admins-only posting rooms, canUserPerformWriteAction returns false because isAllowedToComment returns false for the admins-only write capability. This means ReportFooter renders only the admins-only banner and does not render ReportActionCompose. When a non-admin member tries to edit their previously sent message on a narrow screen, the edit state is triggered but the bottom composer is absent, so the edit cannot be completed.