[Due for payment 2025-02-27] Expense details - Violation is not displayed on description field when opening IOU details

[IuliiaHerets]

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.0.94-1
Reproducible in staging?: Yes
Reproducible in production?: No
Email or phone of affected tester (no customers): expensify416+da2@gmail.com
Issue reported by: Applause Internal Team
Device used: MacOS Chrome, Desktop
App Component: Money Requests

Action Performed:

1. Create a workspace
2. Create an IOU request in the workspace chat with a category (Advertising)
3. Go to Reports page
4. Go to workspace settings page > Categories
5. Disable the category you have selected on step 2
6. Return to Reports page
7. Click on Review button of the money request

Expected Result:

Violation should be displayed on Category field on the first visit to the IOU details page

Actual Result:

Violation is not displayed on Category field on the first visit to the IOU details page

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6732946_1738660825917.category_violations.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @michaelkwardrop

[melvin-bot]

Triggered auto assignment to @mjasikowski (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @michaelkwardrop (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]

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

[IuliiaHerets]

Production behavior

bandicam.2025-02-04.11-42-58-458.mp4

[mjasikowski]

I'll check a few PRs to see if this is connected