Expense-"Multiple attendees required for this category" appears when splitting expense offline

[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.2.84-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: #76687
Email or phone of affected tester (no customers): sdjoidsjoisjndoi2@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Rules are enabled.
• Enable Attendee tracking in Rules.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories.
3. Open Advertising settings.
4. Click Require fields.
5. Enable Require attendees.
6. Go back to workspace chat.
7. Create an expense with Advertising category and two attendees.
8. Open expense report.
9. Go offline.
10. Click More > Split > Save.

Expected Result:

"Multiple attendees required for this category" will not appear because the splits have two attendees.

Actual Result:

"Multiple attendees required for this category" appears when splitting expense offline when the splits have two attendees.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7033730_1766153589191.26.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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