[HOLD for payment 2024-04-15] [Violations][$500] Scan - Category row shows violation briefly after the scan request is created

[kavimuru]

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: 1.4.50-2
Reproducible in staging?: y
Reproducible in production?: y
Issue reported by: applause internal team

Action Performed:

Precondition:

• User is an employee of Collect workspace.
• The Collect workspace has toggled on "People must categorize expenses" for Categories on Old Dot.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create a scan request without category.
4. Go to request details page right after it is created.

Expected Result:

Category row will not show violation until after smartscanning is complete.

Actual Result:

Category row shows "missing category" violation briefly after the scan request is created.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6410628_1710216751744.20240312_120823.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01e13a4e6b1d86de89
• Upwork Job ID: 1770584960942833664
• Last Price Increase: 2024-03-20
• Automatic offers:
• eh2077 | Reviewer | 0
• bernhardoj | Contributor | 0

[melvin-bot]

Triggered auto assignment to @bfitzexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[kavimuru]

We think this bug might be related to #wave-collect - RELEASE 1

cc @trjExpensify

[kavimuru]

@bfitzexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[trjExpensify]

Hm, why wouldn't we show the category violation right away if categories are required on the workspace? 🤔 CC: @JmillsExpensify @cead22

[bfitzexpensify]

Yes, I think the bug here is that the violation disappears, not that it appears in the first place.

[bfitzexpensify]

@trjExpensify do you agree with this comment?

If so, I'll update the OP and send external

[trjExpensify]

Yeah, I agree with it insofar as I don't know why it's disappearing. This is violations related though, so one for #wave-control. :)