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 [email protected] 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): [email protected]
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

[mjasikowski]

Unable to reproduce on dev or staging:

Screen.Recording.2025-02-04.at.13.17.32.mov

I suspect this may have something to do with Onyx update speed.

[samranahm]

@mjasikowski I can still repo this, here's how

• make sure you don't already have any disabled category
• Previous openReport expenses have been paid

Screen.Recording.2025-02-04.at.8.16.46.PM.mov

[mjasikowski]

Will try to reproduce once again

[mjasikowski]

Managed to reproduce, looking for a fix now

[mjasikowski]

This is caused by #54455, creating a revert
FYI @Krishna2323 @rojiphil

[Krishna2323]

@mjasikowski, if we have some time then I can try fixing this with a follow-up PR.

[mjasikowski]

@Krishna2323 how long would it take for you to make a PR?

[Krishna2323]

I think 2 hours should be enough for finding a solution and raising the PR but I will try to finish that asap.

[mjasikowski]

all right, I think we can wait a couple of hours - I will most likely be done by that time so please post in #expensify-open-source when ready

[rojiphil]

PR is ready for internal review. Thanks.
cc @mjasikowski

[kavimuru]

Not reproducible

Recording.571.mp4

[luacmartins]

We reverted the original PR, please work on reimplementing the PR with the blocker in mind.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.95-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Revert "Merge pull request #54455 from Krishna2323/krishna2323/issue/… #56476

If no regressions arise, payment will be issued on 2025-02-18. 🎊

[melvin-bot]

@mjasikowski / @roryabraham @michaelkwardrop @mjasikowski / @roryabraham The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]