You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-01-27] Invoice - "Multiple attendees required for this category" appears on invoice row #79707
Version Number: 9.3.3-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:#79050 Email or phone of affected tester (no customers):sjnodijsodijsoijsio@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.1 / Chrome App Component: Search
Action Performed:
Preconditions:
Rules are enabled.
Enable Attendee tracking in Rules.
Make Advertising category require attendees in category settings.
Invoice is enabled.
Go to staging.new.expensify.com
Open FAB > Send invoice.
Enter amount > Next.
Select a user > Next.
On confirm page, select Advertising category.
Send the invoice.
Go to Reports > Expenses.
Click Type dropdown.
Select Invoice and click Apply.
Expected Result:
"Multiple attendees required for this category" will not appear on invoice row.
Actual Result:
"Multiple attendees required for this category" appears on invoice row.
👋 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:
Identify the pull request that introduced this issue and revert it.
Classification: Frontend bug Causing PR: #79050 - "feat: add ability to require attendees based on category selection (rework)" by @ikevin127 (High confidence) Related Issues: #79008 (invoice submission issue that was fixed in the same PR)
Recommendation: ROLL FORWARD
The causing PR is clear and the fix is straightforward. A small patch to add the invoice check in the search list display logic is simpler than reverting this large feature PR that adds the "require attendees for category" functionality.
Labels: Keeping DeployBlockerCash (frontend bug in App requires App fix)
Detailed Analysis
Evidence
PR #79050 added the ability to require attendees based on category selection. The PR correctly handles invoice validation during submission by adding a check in MoneyRequestConfirmationList.tsx that skips the validation when iouType !== CONST.IOU.TYPE.INVOICE. This prevents the validation from blocking invoice submission. However, the violation still appears in the Search/Reports list view because TransactionListItem.tsx does not have the same check.
The syncMissingAttendeesViolation() function is called without checking if the transaction belongs to an invoice report. PR #79050 merged on 2026-01-14 and aligns with when this bug appeared in staging (version 9.3.3-0).
Root Cause
The PR has two code paths for handling the missingAttendees violation:
Display in search list (TransactionListItem.tsx): Missing the invoice check
The fix should add a check for reportForViolations?.type === CONST.REPORT.TYPE.INVOICE before calling syncMissingAttendeesViolation() to skip invoice transactions.
changed the title [-]Invoice - "Multiple attendees required for this category" appears on invoice row[/-][+][Due for payment 2026-01-27] Invoice - "Multiple attendees required for this category" appears on invoice row[/+]on Jan 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.4-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@JS00001@JmillsExpensify 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]
Activity
melvin-bot commentedon Jan 15, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #79050
melvin-bot commentedon Jan 15, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 15, 2026
Triggered auto assignment to @JmillsExpensify (
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 commentedon Jan 15, 2026
👋 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:
OSBotify commentedon Jan 15, 2026
Investigation Summary
Classification: Frontend bug
Causing PR: #79050 - "feat: add ability to require attendees based on category selection (rework)" by @ikevin127 (High confidence)
Related Issues: #79008 (invoice submission issue that was fixed in the same PR)
Recommendation: ROLL FORWARD
The causing PR is clear and the fix is straightforward. A small patch to add the invoice check in the search list display logic is simpler than reverting this large feature PR that adds the "require attendees for category" functionality.
Labels: Keeping
DeployBlockerCash(frontend bug in App requires App fix)Detailed Analysis
Evidence
PR #79050 added the ability to require attendees based on category selection. The PR correctly handles invoice validation during submission by adding a check in
MoneyRequestConfirmationList.tsxthat skips the validation wheniouType !== CONST.IOU.TYPE.INVOICE. This prevents the validation from blocking invoice submission. However, the violation still appears in the Search/Reports list view becauseTransactionListItem.tsxdoes not have the same check.Verification
Affected file:
src/components/SelectionListWithSections/Search/TransactionListItem.tsx(lines 159-167)The
syncMissingAttendeesViolation()function is called without checking if the transaction belongs to an invoice report. PR #79050 merged on 2026-01-14 and aligns with when this bug appeared in staging (version 9.3.3-0).Root Cause
The PR has two code paths for handling the
missingAttendeesviolation:The fix should add a check for
reportForViolations?.type === CONST.REPORT.TYPE.INVOICEbefore callingsyncMissingAttendeesViolation()to skip invoice transactions.JS00001 commentedon Jan 15, 2026
Going to CP a fix here to disable the feature: #79620
ikevin127 commentedon Jan 15, 2026
🗒️ Noted for follow-up PR.
1 remaining item
IuliiaHerets commentedon Jan 16, 2026
Chrome / 9.3.3-2
No Attendees in required fields, only Description
Screen.Recording.2026-01-16.at.10.49.41.mp4
JS00001 commentedon Jan 16, 2026
CP'd a fix to hide this feature, closing. @ikevin127 Lets fix this in a follow up
[-]Invoice - "Multiple attendees required for this category" appears on invoice row[/-][+][Due for payment 2026-01-27] Invoice - "Multiple attendees required for this category" appears on invoice row[/+]melvin-bot commentedon Jan 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.4-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-01-27. 🎊
melvin-bot commentedon Jan 20, 2026
@JS00001 @JmillsExpensify 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]