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
Invoice - "Hidden" is selected on recipient list instead of invoice chat #82459
Version Number: 9.3.19-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#78354 Email or phone of affected tester (no customers):oisdjoisjdiojisojsd@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.2 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Invoice is enabled.
User has sent an invoice.
Go to staging.new.expensify.com
Open FAB > Send invoice.
Enter amount > Next.
Select invoice chat.
On confirm page, click To field.
Click RHP back button until you reach amount input page.
Click Next.
On confirm page, click To field.
Expected Result:
Invoice chat will be selected.
Actual Result:
"Hidden" is selected instead of invoice chat.
If user clicks on the "Hidden" chat, To field changes to Unavailable workspace.
So reportID-only invoice participants were not treated as report options and fell through to getParticipantsOption(), which has no login/accountID here and renders as Hidden.
What changes do you think we should make in order to solve the problem?
Use robust invoice detection in selected-option mapping by checking the actual report type from reportID (while keeping existing checks), so reportID-only participants are still handled as invoice rooms. Update this :
Activity
melvin-bot commentedon Feb 13, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #78354
melvin-bot commentedon Feb 13, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 13, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eh2077 (
External)melvin-bot commentedon Feb 13, 2026
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.
melvin-bot commentedon Feb 13, 2026
Triggered auto assignment to @sonialiap (
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.5 remaining items
marufsharifi commentedon Feb 15, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
Invoice - "Hidden" is selected on recipient list instead of invoice chat
What is the root cause of that problem?
There is a data-shape mismatch for invoice participants after back navigation.
getMoneyRequestParticipantsFromReport()stores invoice participant as reportID-only:App/src/libs/actions/IOU/index.ts
Lines 12302 to 12311 in a93a316
But in
formatSectionsFromSearchTerm(), invoice detection was too strict and expectedaccountID === 0plusiouType === 'invoice':App/src/libs/OptionsListUtils/index.ts
Lines 2783 to 2793 in a93a316
So reportID-only invoice participants were not treated as report options and fell through to
getParticipantsOption(), which has nologin/accountIDhere and renders as Hidden.What changes do you think we should make in order to solve the problem?
Use robust invoice detection in selected-option mapping by checking the actual report type from
reportID(while keeping existing checks), soreportID-onlyparticipants are still handled as invoice rooms.Update this :
App/src/libs/OptionsListUtils/index.ts
Line 2785 in a93a316
To This :
reportIDandgetReportOrDraftReport(reportID)is an invoice room, map withgetReportOption().What alternative solutions did you explore? (Optional)
Demo
82459.mp4
mountiny commentedon Feb 15, 2026
Testing a revert here #82524
melvin-bot commentedon Feb 15, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
m-natarajan commentedon Feb 16, 2026
Issue not reproduce using v9.3.19-1 PR:82524
Screen.Recording.2026-02-16.at.7.31.13.AM.mov
melvin-bot commentedon Feb 16, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
IuliiaHerets commentedon Feb 16, 2026
@mountiny Chrome / v9.3.19-4
Not repro
Screen.Recording.2026-02-16.at.13.22.01.mp4