[$250] Expense - "Category no longer valid" error appears offline but disappears when back 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: 9.1.69-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: #62234
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Web, mweb
App Component: Money Requests

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Sign in with a new gmail account
3. Go offline
4. Create a new workspace.
5. Create a manual expense with a category.
6. Go to the category page.
7. Delete the category used in step 5.
8. Go back to the expense report.
9. Confirm the category field displays a violation that reads "Category no longer valid".
10. Go online.

Expected Result:

The error should persist even after the device is back online.

Actual Result:

The error disappears when the device goes online.

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

Bug6864231_1750308626727.bandicam_2025-06-19_07-49-32-349.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021935619928614896675
• Upwork Job ID: 1935619928614896675
• Last Price Increase: 2025-06-26

Issue Owner

Current Issue Owner: @ahmedGaber93

[melvin-bot]

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

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

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