Fix duplicate phone invitee and lost selection in approval workflow Expenses from

[MelvinBot]

Explanation of Change

When you invite an approver by phone number in the approval-workflow "Expenses from" flow, the same person is tracked under two different key formats:

• approvalWorkflow.members[].email and the invite draft use the bare E.164 form, e.g. +15551234567 (the picker's userToInvite.login has no SMS domain).
• After the invite completes, policy.employeeList is keyed by the SMS-domain form, e.g. +15551234567@expensify.sms, because addMembersToWorkspace runs every login through addSMSDomainIfPhoneNumber.

Because +15551234567 ≠ +15551234567@expensify.sms, every lookup that bridges the staged member to the live policy member missed, which caused both reported symptoms:

• Duplicate row: the allApprovers dedup compared the selected member's bare login against the policy member's SMS-domain login, so the invitee rendered once as the selected entry and again as the policy member.
• Lost selection on back: goBack and the selection-sync effect kept only members found in employeeList by their bare email, so the just-invited member was treated as "never invited" and dropped.

The fix normalizes the phone login to its SMS-domain form (via addSMSDomainIfPhoneNumber) at each policy.employeeList lookup — in the sync effect, the allApprovers dedup, goBack, nextStep, and toggleMember. The invite-draft keys are intentionally left in the bare E.164 form so the shared invite-message page keeps displaying the plain phone number (it surfaces the raw draft key) and stays consistent with the regular invite flow. addSMSDomainIfPhoneNumber is a no-op for emails and already-suffixed phone numbers, so this is safe for email invitees and existing members too.

Fixed Issues

$ #93621
PROPOSAL: #93621 (comment)

Tests

1. Go to a workspace's Workspace settings > Workflows (upgrade the workspace if needed).
2. Click Add approval workflow.
3. In the Expenses from step, enter a phone number that does not have a New Expensify account, select it, and tap Next.
4. Tap Invite, select any approver, then tap Skip.
5. On the confirm page, tap Expenses from.
6. Verify the invited phone number appears exactly once in the list.
7. Tap the RHP back button and verify the phone number remains selected.
8. Repeat steps 1-7 inviting by email instead and verify behavior is unchanged.

• Verify that no errors appear in the JS console

Offline tests

Same as Tests.

QA Steps

1. Go to a workspace's Workspace settings > Workflows (upgrade the workspace if needed).
2. Click Add approval workflow.
3. In the Expenses from step, enter a phone number that does not have a New Expensify account, select it, and tap Next.
4. Tap Invite, select any approver, then tap Skip.
5. On the confirm page, tap Expenses from.
6. Verify the invited phone number appears exactly once in the list.
7. Tap the RHP back button and verify the phone number remains selected.
8. Repeat steps 1-7 inviting by email instead and verify behavior is unchanged.

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[github-actions]

🚧 @youssef-lr has triggered a test Expensify/App build. You can view the workflow run here.

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
...ls/WorkspaceWorkflowsApprovalsExpensesFromPage.tsx	0.00% <0.00%> (ø)
... and 21 files with indirect coverage changes

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #93640.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-486a97144fe-d12cd93-5bfdf2fbd6b61d26df62a0e4ecc329053b8b6cf9/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-486a971-d12cd93-473c8c4f32d26c826536223299d5fff474c25fa7/index.html

Web 🕸️
https://93640.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀