Expense - Expense disappear from workspace after editing any fields in expense details

[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.7-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-3292/folder/13177075/41703290/1143584140, https://test-management.browserstack.com/projects/2219752/test-runs/TR-3292/folder/13176744/41237145/1143583583, https://test-management.browserstack.com/projects/2219752/test-runs/TR-3292/folder/13176744/41237150/1143583587
Email or phone of affected tester (no customers): kiatest.80+ck1222630@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11/Chrome
App Component: Money Requests

Action Performed:

Issue: 1

1. Navigate to staging.new.expensify.com
2. Create new account & workspace
3. Submit manual expense in workspace chat
4. Open the submitted report
   5.Edit any of the following field - Merchant, Amount , Category, Date
5. Observe expense disappears from workspace chat

Issue 2:

1. Navigate to staging.new.expensify.com
2. Submit manual expense in workspace chat
3. Long Press on expense & select Hold option
4. Enter reason & save it
5. Observe expense disappears from workspace chat

Expected Result:

Expense should not disappear from workspace after editing any fields in expense details page & while holding the expense

Note : Issue happens when editing distance expense as well.

Actual Result:

Expense disappear from workspace after editing any fields in expense details & while holding the expense

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

2.mp4

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @greg-schroeder (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 @JS00001 (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 in progress. Checking recent PRs that might affect expense visibility in workspace chats.

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug (requires App code fix)
Causing PR: Unable to determine with high confidence - NEEDS INVESTIGATION
Related Issues: None identified

Recommendation: NEEDS INVESTIGATION

This is a critical deploy blocker affecting core expense functionality, but I cannot identify the specific causing PR with confidence. The issue is complex:

1. The bug appears ONLY on staging 9.3.7-1, not in production
2. Symptoms: Expenses disappear from workspace chat after editing fields (Merchant, Amount, Category, Date) or after holding the expense
3. The issue was reported at 2026-01-23T05:05:34Z, which is ~5.5 hours AFTER PR Update create transaction Manual flow to ask for merchant after asking for amount #76595 was reverted via PR Revert "Update create transaction Manual flow to ask for merchant after asking for amount" #80286 (merged at 2026-01-22T23:39:35Z)
4. Therefore, PR Update create transaction Manual flow to ask for merchant after asking for amount #76595 is NOT the cause despite multiple other issues being attributed to it

Action Items:

• @jponikarchuk (issue reporter) - Can you provide more details about what "disappear" means? Does the expense report completely vanish from the LHN? Does it show as archived? Does the preview disappear but the report remains?
• @JS00001 @greg-schroeder - This needs immediate triage by someone who can reproduce the issue on staging
• Investigate recent PRs in deploy 9.3.7-1 that touch:
  • Report visibility logic (shouldHideReport, isHiddenForCurrentUser)
  • Transaction editing flows
  • Money request preview display logic
  • Hold expense functionality

Labels: Keeping DeployBlockerCash (this is a frontend bug affecting the App)

📋 Detailed Analysis

Evidence

• Version 9.3.7-1 staging only, not reproducible in production
• Issue affects both editing expense fields AND holding expenses
• Both scenarios result in expense "disappearing" from workspace chat
• Affects Windows/Chrome and Android App platforms

Verification Attempted

I reviewed the current StagingDeployCash PRs and recent changes to expense/report handling code:

• PR Update create transaction Manual flow to ask for merchant after asking for amount #76595 (manual expense merchant flow) was already reverted in Revert "Update create transaction Manual flow to ask for merchant after asking for amount" #80286 before this issue was reported
• PR fix: Self DM appears twice in Recents section #79640 (Self DM appears twice) was reverted in Revert "fix: Self DM appears twice in Recents section" #80257 due to type check issues
• PR fix: Offline expense shows Outstanding from report but Paid from chat #79536 (Offline expense status) - unlikely to cause disappearing expenses
• No obvious recent changes to report visibility logic in the timeframe

Root Cause

Unable to determine without reproduction. The issue likely involves:

• Report hiding/archiving logic being triggered incorrectly after edits
• Transaction state changes causing the money request preview to be hidden
• Report participant changes causing visibility issues

Requires hands-on debugging with reproduction steps on staging environment.