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
[$250] Expense - “To” field is not tappable on confirm page with Expensifail account #83534
Version Number: 9.3.26-4 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:#81284 Email or phone of affected tester (no customers):applausetester+nowe@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Samsung Galaxy S21 Ultra/Android 15, Macbook/macOS 13.7.8/Chrome. iPhone 13/18.6.2 App Component: Other
Action Performed:
Precondition: Log in to Expensifail account.
Launch Expensify app.
Open FAB > Create expense > Manual.
Enter amount > Next.
On confirm page, tap To field.
Expected Result:
Contact list will always auto load when scrolled to the bottom.
Actual Result:
The “To” field cannot be tapped or selected on the Confirm page and user is unable to access to contact list
changed the title [-]Expense - “To” field is not tappable on confirm page with Expensifail account[/-][+][$250] Expense - “To” field is not tappable on confirm page with Expensifail account[/+]on Feb 26, 2026
Please re-state the problem that we are trying to solve in this issue.
The "To" field cannot be tapped or selected on the Confirm page and user is unable to access to contact list.
What is the root cause of that problem?
In MoneyRequestConfirmationList.tsx, the isInteractive and shouldShowRightCaret properties for the "To" field participant row include a (!isRestrictedToPreferredPolicy || isTypeInvoice) condition. When the user's domain has a security group with enableRestrictedPrimaryPolicy set to true and a valid restrictedPrimaryPolicyID, isRestrictedToPreferredPolicy becomes true, which causes isInteractive to evaluate to false for non-invoice expense types. This makes the "To" field row completely non-tappable on the confirmation page.
However, this restriction is unnecessary here because the MoneyRequestParticipantsSelector already passes isRestrictedToPreferredPolicy and preferredPolicyID to the options filtering logic, which correctly limits the participant choices to only those within the preferred policy. So the participant selection page itself already enforces the restriction — there is no need to also block navigation to it from the confirmation page.
What changes do you think we should make in order to solve the problem?
Remove the (!isRestrictedToPreferredPolicy || isTypeInvoice) condition from isInteractive and shouldShowRightCaret in MoneyRequestConfirmationList.tsx, since the participant selector already handles the policy restriction by filtering the available options.
After this change, isRestrictedToPreferredPolicy and isTypeInvoice can also be removed from the useMemo dependency array of sections.
Optional: we can keep the isTypeInvoice in the condition
What alternative solutions did you explore? (Optional)
An alternative would be to add a separate check inside navigateToParticipantPage to handle the restricted policy case differently (e.g., navigate to a filtered participant page). However, since the participant selector already filters options based on isRestrictedToPreferredPolicy, this would be redundant. The simplest and most correct fix is to remove the overly restrictive condition on the confirmation page.
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
Please re-state the problem that we are trying to solve in this issue.
The "To" field on the expense confirmation page (Create expense > Manual > Enter amount > Next) cannot be tapped or selected when using an Expensifail account. This prevents users from accessing the contact list to change the expense recipient.
What is the root cause of that problem?
The "To" field's interactivity is controlled by the following expression in MoneyRequestConfirmationList.tsx (line 843):
For Expensifail accounts, the domain's security group has enableRestrictedPrimaryPolicy set to true with a valid restrictedPrimaryPolicyID. This causes usePreferredPolicy() (hook source) to return isRestrictedToPreferredPolicy: true.
When isRestrictedToPreferredPolicy is true and the expense type is not an invoice, the condition (!isRestrictedToPreferredPolicy || isTypeInvoice) evaluates to false, which makes isInteractive = false. This flows through BaseListItem → PressableWithFeedback → BaseGenericPressable, where the press handler returns early when interactive is false (line 112).
This restriction is overly broad. The MoneyRequestParticipantsSelector already passes isRestrictedToPreferredPolicy and preferredPolicyID into the options filtering logic (lines 192-193), which correctly limits the visible contacts to the preferred policy. Blocking access to the participant selector page entirely from the confirmation page is redundant and breaks the UX.
What changes do you think we should make in order to solve the problem?
Remove the (!isRestrictedToPreferredPolicy || isTypeInvoice) sub-condition from both the isInteractive and shouldShowRightCaret expressions in MoneyRequestConfirmationList.tsx (around line 843-844). The updated expressions should be:
This is safe because the participant selector page already enforces the preferred policy restriction by filtering which contacts are shown. Users will be able to tap the "To" field and see a filtered contact list, but they will only see contacts within their restricted policy.
What alternative solutions did you explore? (Optional)
An alternative would be to modify usePreferredPolicy to not return isRestrictedToPreferredPolicy: true for certain account types, but this would be incorrect as the restriction should still apply at the participant filtering level — just not at the "To" field tappability level.
Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, or @MelvinBot <your feedback> to refine this analysis.
Please re-state the problem that we are trying to solve in this issue.
On the Expense confirmation step, the “To” row is not tappable for Expensifail users, so they cannot open the participant selector and cannot continue with recipient selection/editing.
What is the root cause of that problem?
The “To” row interactivity is gated by a condition that disables the row when the account is restricted to a preferred policy:
Root-cause condition in MoneyRequestConfirmationList :
That makes the row non-interactive, which blocks tapping entirely.
This is over-restrictive because participant restriction is already enforced inside the selector options filtering :
What changes do you think we should make in order to solve the problem?
I implemented a stronger fix by centralizing participant editability into one reusable rule and using it in both UI interactivity and navigation gating.
1) Add a single source of truth helper in IOUUtils
After fixing this problem, we still have another problem in the participant page: the DM contact appears in the participant list while isRestrictedToPreferredPolicy is true.
Screen.Recording.2026-02-26.at.13.29.04.mov
We also need to fix this to prevent submitting the expense to DM when isRestrictedToPreferredPolicy is true. We need to update this condition to not include the DM options when isRestrictedToPreferredPolicy is true
if (includeP2P && !config.isRestrictedToPreferredPolicy) {
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
Activity
melvin-bot commentedon Feb 26, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee (
External)melvin-bot commentedon Feb 26, 2026
Triggered auto assignment to @heyjennahay (
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.melvin-bot commentedon Feb 26, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022026893792994641346
[-]Expense - “To” field is not tappable on confirm page with Expensifail account[/-][+][$250] Expense - “To” field is not tappable on confirm page with Expensifail account[/+]daledah commentedon Feb 26, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
The "To" field cannot be tapped or selected on the Confirm page and user is unable to access to contact list.
What is the root cause of that problem?
In
MoneyRequestConfirmationList.tsx, theisInteractiveandshouldShowRightCaretproperties for the "To" field participant row include a(!isRestrictedToPreferredPolicy || isTypeInvoice)condition. When the user's domain has a security group withenableRestrictedPrimaryPolicyset totrueand a validrestrictedPrimaryPolicyID,isRestrictedToPreferredPolicybecomestrue, which causesisInteractiveto evaluate tofalsefor non-invoice expense types. This makes the "To" field row completely non-tappable on the confirmation page.App/src/components/MoneyRequestConfirmationList.tsx
Lines 843 to 844 in a152afa
However, this restriction is unnecessary here because the
MoneyRequestParticipantsSelectoralready passesisRestrictedToPreferredPolicyandpreferredPolicyIDto the options filtering logic, which correctly limits the participant choices to only those within the preferred policy. So the participant selection page itself already enforces the restriction — there is no need to also block navigation to it from the confirmation page.App/src/pages/iou/request/MoneyRequestParticipantsSelector.tsx
Lines 192 to 193 in a152afa
What changes do you think we should make in order to solve the problem?
Remove the
(!isRestrictedToPreferredPolicy || isTypeInvoice)condition fromisInteractiveandshouldShowRightCaretinMoneyRequestConfirmationList.tsx, since the participant selector already handles the policy restriction by filtering the available options.After this change,
isRestrictedToPreferredPolicyandisTypeInvoicecan also be removed from theuseMemodependency array ofsections.Optional: we can keep the
isTypeInvoicein the conditionWhat alternative solutions did you explore? (Optional)
An alternative would be to add a separate check inside
navigateToParticipantPageto handle the restricted policy case differently (e.g., navigate to a filtered participant page). However, since the participant selector already filters options based onisRestrictedToPreferredPolicy, this would be redundant. The simplest and most correct fix is to remove the overly restrictive condition on the confirmation page.Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
MelvinBot commentedon Feb 26, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
The "To" field on the expense confirmation page (Create expense > Manual > Enter amount > Next) cannot be tapped or selected when using an Expensifail account. This prevents users from accessing the contact list to change the expense recipient.
What is the root cause of that problem?
The "To" field's interactivity is controlled by the following expression in
MoneyRequestConfirmationList.tsx(line 843):For Expensifail accounts, the domain's security group has
enableRestrictedPrimaryPolicyset totruewith a validrestrictedPrimaryPolicyID. This causesusePreferredPolicy()(hook source) to returnisRestrictedToPreferredPolicy: true.When
isRestrictedToPreferredPolicyistrueand the expense type is not an invoice, the condition(!isRestrictedToPreferredPolicy || isTypeInvoice)evaluates tofalse, which makesisInteractive=false. This flows throughBaseListItem→PressableWithFeedback→BaseGenericPressable, where the press handler returns early wheninteractiveisfalse(line 112).This restriction is overly broad. The
MoneyRequestParticipantsSelectoralready passesisRestrictedToPreferredPolicyandpreferredPolicyIDinto the options filtering logic (lines 192-193), which correctly limits the visible contacts to the preferred policy. Blocking access to the participant selector page entirely from the confirmation page is redundant and breaks the UX.What changes do you think we should make in order to solve the problem?
Remove the
(!isRestrictedToPreferredPolicy || isTypeInvoice)sub-condition from both theisInteractiveandshouldShowRightCaretexpressions inMoneyRequestConfirmationList.tsx(around line 843-844). The updated expressions should be:This is safe because the participant selector page already enforces the preferred policy restriction by filtering which contacts are shown. Users will be able to tap the "To" field and see a filtered contact list, but they will only see contacts within their restricted policy.
What alternative solutions did you explore? (Optional)
An alternative would be to modify
usePreferredPolicyto not returnisRestrictedToPreferredPolicy: truefor certain account types, but this would be incorrect as the restriction should still apply at the participant filtering level — just not at the "To" field tappability level.Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR, or@MelvinBot <your feedback>to refine this analysis.marufsharifi commentedon Feb 26, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
On the Expense confirmation step, the “To” row is not tappable for Expensifail users, so they cannot open the participant selector and cannot continue with recipient selection/editing.
What is the root cause of that problem?
The “To” row interactivity is gated by a condition that disables the row when the account is restricted to a preferred policy:
MoneyRequestConfirmationList:App/src/components/MoneyRequestConfirmationList.tsx
Lines 843 to 844 in a152afa
For Expensifail accounts,
usePreferredPolicy()returnsisRestrictedToPreferredPolicy: true:App/src/hooks/usePreferredPolicy.ts
Lines 39 to 41 in a152afa
That makes the row non-interactive, which blocks tapping entirely.
This is over-restrictive because participant restriction is already enforced inside the selector options filtering :
App/src/pages/iou/request/MoneyRequestParticipantsSelector.tsx
Lines 192 to 193 in a152afa
What changes do you think we should make in order to solve the problem?
I implemented a stronger fix by centralizing participant editability into one reusable rule and using it in both UI interactivity and navigation gating.
1) Add a single source of truth helper in
IOUUtils2) Use the helper in
MoneyRequestConfirmationListfor both row behavior and navigationThis fixes the bug and keeps policy restriction where it belongs: in participant option filtering, not in blocking the tap path.
What alternative solutions did you explore? (Optional)
(!isRestrictedToPreferredPolicy || isTypeInvoice)inline) was considered.nkdengineer commentedon Feb 26, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
The “To” field cannot be tapped or selected on the Confirm page and user is unable to access to contact list
What is the root cause of that problem?
For the account that is in a restricted domain, we block the
Tofield here becauseisRestrictedToPreferredPolicyistrueApp/src/components/MoneyRequestConfirmationList.tsx
Lines 843 to 844 in a152afa
What changes do you think we should make in order to solve the problem?
For the restricted domain account, we have two participant options to create an expense
So we can allow editing the participant by removing
(!isRestrictedToPreferredPolicy || isTypeInvoice)condition from hereApp/src/components/MoneyRequestConfirmationList.tsx
Lines 843 to 844 in a152afa
After fixing this problem, we still have another problem in the participant page: the DM contact appears in the participant list while
isRestrictedToPreferredPolicyistrue.Screen.Recording.2026-02-26.at.13.29.04.mov
We also need to fix this to prevent submitting the expense to DM when
isRestrictedToPreferredPolicyistrue. We need to update this condition to not include the DM options whenisRestrictedToPreferredPolicyistrueApp/src/libs/OptionsListUtils/index.ts
Line 2566 in a152afa
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
30 remaining items
melvin-bot commentedon Mar 24, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Apr 6, 2026
@heyjennahay Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Apr 8, 2026
@heyjennahay Huh... This is 4 days overdue. Who can take care of this?
heyjennahay commentedon Apr 8, 2026
Payment summary
Thanks everyone
laurenreidexpensify commentedon Apr 10, 2026
Payment Approved for @jjcoffee in New Expensify $125
twisterdotcom commentedon Apr 22, 2026
@nkdengineer has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-616f-a8f8-adc8-584179b9d454