[Due for payment 2025-10-01] Expense- Reject system messages disappear after going back to online

[mitarachim]

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: v9.2.14-4
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 TestRail: #62787
Email or phone of affected tester (no customers): applausetester+ndk20@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 11/iOS 18.6/ Safari
App Component: Money Requests

Action Performed:

Precondition: Use WS admin and create 1 single expense report

1. Open https://staging.new.expensify.com/
2. Navigate to single expense report
3. Go offline
4. Submit the expense
5. Tap on 'More' > 'Reject'
6. Enter a reason and tap on 'Reject expense'
7. Tap on 'Mark as resolved'
8. Repeat Step 4 - Step 6
9. Go back online

Expected Result:

System msgs should be shown fully

Actual Result:

Reject system msgs disappears after going back online. In Web, msgs are listed in wrong order. Navigate away and back will solve it.

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

Bug6945540_1757984557412.System_Msg_Disappears.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @garrettmknight

[melvin-bot]

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