[Due for payment 2026-06-18] Spend - "fragment.text" appears after deleting the thread conversation

[applause-bot]

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.81-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #90680
Email or phone of affected tester (no customers): bomoj13395@bittnex.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:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create two expenses.
4. Go to Spend > Reports.
5. Open the report.
6. Open any expense.
7. Send a message in transaction thread.
8. Right click on the message > Reply in thread.
9. Send a reply in thread.
10. Delete the parent message by right click on the message > Delete comment.
11. Delete the thread reply by right click on the message > Delete comment.

Expected Result:

"fragment.text" will not appear after deleting the thread conversation.

Actual Result:

"fragment.text" appears after deleting the thread conversation.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7162651_1779710903167.2.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7162651

Issue Owner

Current Issue Owner: @mkhutornyi

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/d48926261317301b2559d555bb88626103f2d27d4405c82d0838e060cadfcd4f

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #90680

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

[MelvinBot]

Proposal

What is the root cause of that problem?

The default case in ReportActionItemFragment.tsx:198 renders the literal string "fragment.text" instead of the JavaScript expression {fragment.text}:

default:
    return <Text>fragment.text</Text>;  // ← literal string, missing curly braces

This default case is reached when a message fragment has a type that doesn't match any handled case (COMMENT, TEXT, LINK, etc.). In transaction threads, IOU report actions can have a non-array message object where the type field is an IOU action type like 'create' or 'delete' (from OriginalMessageIOU) rather than a message fragment type like 'COMMENT'. When getReportActionMessageFragments wraps this non-array message into an array, the fragment carries the IOU action type, causing the switch to fall through to default.

PR #90680 changed thread navigation into the RHP, which now renders the parent IOU action through ReportActionItemFragment in a code path that wasn't previously exercised — making the latent bug visible.

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

Fix the default case in ReportActionItemFragment.tsx:198 to use a JSX expression:

default:
    return <Text>{fragment.text}</Text>;

This ensures that when an unrecognized fragment type is encountered, the actual text content is displayed instead of the literal string "fragment.text".

What alternative solutions did you explore?

An alternative would be to fix getReportActionMessageFragments to normalize IOU action types to 'COMMENT' when wrapping non-array messages. However, the simpler and more defensive fix is correcting the default case — it should never render a literal string regardless of what fragment types flow through it.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[ShreyasPatil3105]

Proposal

What is the root cause of that problem?

In src/components/ReportActionItemFragment.tsx, the default case of the fragment type switch block renders the literal string "fragment.text" rather than evaluating it as a JSX expression. When a transaction thread message or IOU action is deleted, the fragment type falls through to this default case, causing the raw variable name string to display on the UI.

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

Update the default return statement in src/components/ReportActionItemFragment.tsx to properly wrap the variable in curly braces:

default:
    return <Text>{fragment.text}</Text>;