[Due for payment 2026-01-16] [Due for payment 2026-01-15] Report - Violation for required attendee, disappears after opening "Attendee" field.

[jponikarchuk]

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.2.95-0
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 BrowserStack: #78315
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 / Chrome (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Workspace is on "Control" policy.
Prerequisite 2: "Rules" and "Attendee tracking" enabled.
Prerequisite 3: "Required attendee" for selected category is enabled.

1. Open the Expensify app.
2. Open any workspace chat.
3. Start a manual expense creation flow.
4. Select a category with "Required Attendee" enabled.
5. Try to submit expense without adding an extra attendee.
6. Note that a "Required attendee" violation appears.
7. Open "Attendee" field and return without adding a new attendee.
8. Note that violation disappears.

Expected Result:

Violation for required attendee, should remain visible when returning from "Attendee" field, if no new attendee was added.

Actual Result:

Violation for required attendee, disappears after opening attendee field and returning to report without adding a new attendee.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @stephanieelliott

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #78315

[melvin-bot]

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

[melvin-bot]

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

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