[Due for payment 2025-07-22] Reports - Removed merchant persists in expense row after removing merchant

[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.80-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: #64761
Email or phone of affected tester (no customers): sjdionsjdodisjois@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.expensify.com
2. Open 1:1 DM
3. Submit an expense with merchant to the user
4. Go to Reports > Expenses
5. Click on the expense row
6. Click Merchant
7. Clear the merchant and save it

Expected Result:

The merchant on the expense row will also be removed

Actual Result:

The merchant on the expense row persists after removing merchant

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

Bug6885029_1752259917158.20250712_024948.mp4

View all open jobs on GitHub

[melvin-bot]

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

[rushatgabhane]

@BlameGPT find the culprits

[BlameGPT]

Sus PRs on the scene

• fix: After clearing merchant and saving it, Merchant field reverts to previous value #63587 #64761: Touched TransactionUtils.getMerchant and added wasMerchantCleared flag altering merchant-display logic, so clearing a merchant could now fail to update the expense row.
• feat: standardize pay button #65296: Overhauled TransactionItemRow (which renders each expense row) while standardising the Pay button, and this may block the component from re-rendering after a merchant is cleared.

If not above, check these

• Fix violation Dot and Message Misaligned in Table View #65070: Changed the HTML renderer for table rows on Reports > Expenses, which could inadvertently leave stale merchant text visible after edits.