Expense RHP turns into skeleton loader after moving invoice to report and disable reimbursable

[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.90-0
Reproducible in staging?: Y
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 TestRail: #63054
Email or phone of affected tester (no customers): ndosijjjosdijs1o@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• Invoice is enabled

1. Go to staging.new.expensify.com
2. Go to workspace chat
3. Submit an expense to the workspace chat
4. Open FAB > Send invoice
5. Send an invoice to any user
6. Open invoice thread
7. Click Report
8. Select the report from Step 3
9. Go to workspace chat and open the expense report
10. Open the expense which is previously an invoice from Step 5
11. Disable reimbursable toggle

Expected Result:

Reimbursable toggle is disabled without issue

Actual Result:

Transaction thread RHP turns into skeleton loader after moving invoice to report and disable reimbursable toggle

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

Bug6909702_1754512820881.20250807_043814.mp4

View all open jobs on GitHub

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

[melvin-bot]

Triggered auto assignment to @alexpensify (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 @madmax330 (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[francoisl]

Will also probably be fixed by #68061