[Due for payment 2025-09-12] Chat - Missing placeholder text in the composer and search field

[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.98-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #67743
Email or phone of affected tester (no customers): sdhshssdjiosdndjs@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Chat Report View

Action Performed:

1. Go to staging.new.expensify.com
2. Open any report.
3. Open search router.

Expected Result:

• Composer will show "Write something" placeholder text.
• Search field will show "Search for someting" placeholder text.

Actual Result:

Composer and search field are missing placeholder text.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @sakluger

[melvin-bot]

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

[blimpich]

Relevant conversation here: https://expensify.slack.com/archives/C049HHMV9SM/p1755884247194659

[ikevin127]

RCA breakdown from the Slack 🧵:

I remember looking at the react-native-live-markdown PRs in between versions 0.1.299 and 0.1.301 and PR: Implement code and pre blocks support on web authored by @BartoszGrajdek was one of the in-between versions PR, my error is that I didn't think to ask about / test those PRs behaviour in E/App to check whether there would be regressions coming from them - I keept things within scope, only testing our PR: Fix/68518 - Strike through is not applied for quote markdown text behaviour.

I wouldn't count this as a regression of our PR, but of Implement code and pre blocks support on web's PR, as for who should handle that IMO the PRs author and we could either:

• revert E/App react-native-live-markdown version back to 0.1.299 to unblock deploy // optionally applying patch of PR: Fix/68518 - Strike through is not applied for quote markdown text to maintain the fix untill react-native-live-markdown is fixed
• have offending PR author open and merge a follow-up react-native-live-markdown PR fixing the issue and then bump the E/App react-native-live-markdown version to the new one including the fix

As for the RCA of this issue, refer to this comment.