fix: Vacation delegate added via phone number changes to @expensify s after clear cache

[paulnjs]

Explanation of Change

Fixed Issues

$#89578
PROPOSAL:#89578 (comment)

Tests

1. Launch app
2. Go to Accounts - status icon
3. Tap vacation delegate - add a phone number eg: +919789942470 and save
4. Tap confirm
5. Note number is displayed properly by reopening the page
6. Go to troubleshoot - clear cache
7. Go to Accounts - status icon
8. Verify the previously selected vacation delegate is displayed original phone number/contact identity without converting to @expensify.sms

• Verify that no errors appear in the JS console

Offline tests

QA Steps

1. Launch app
2. Go to Accounts - status icon
3. Tap vacation delegate - add a phone number eg: +919789942470 and save
4. Tap confirm
5. Note number is displayed properly by reopening the page
6. Go to troubleshoot - clear cache
7. Go to Accounts - status icon
8. Verify the previously selected vacation delegate is displayed original phone number/contact identity without converting to @expensify.sms

• 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

Screen.Recording.2026-07-02.at.15.49.03.mov

Android: mWeb Chrome

iOS: Native

Screen.Recording.2026-07-02.at.15.39.11.mov

iOS: mWeb Safari

Screen.Recording.2026-07-02.at.15.13.06.mov

MacOS: Chrome / Safari

Screen.Recording.2026-07-02.at.15.06.29.mov

[melvin-bot]

@sobitneupane Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[trjExpensify]

Yep, we shouldn't be showing +@expensify.sms in the product. 👍

[sobitneupane]

@paulnjs Could you please add tests and screen recordings for the existing account (Phone Number) as well? Let me know once it's updated.

[sobitneupane]

@paulnjs Could you please check the following screenshot from your recording?

As mentioned in this comment in this issue, the format should be:

[paulnjs]

@sobitneupane I updated. Don't know why but i can not open app through dev domain on android chorme. Could you please help to check it on your side?

[sobitneupane]

Sorry for the delay. I will try to review it by EOD tomorrow NPT.

[sobitneupane]

@paulnjs The changes still doesn't match the expectation.

Expectation:

After update:

[paulnjs]

@sobitneupane I updated. Could you please help to check? The failed test comes from main, I will sync main later after it's fixed

[sobitneupane]

@paulnjs Sorry for the delay. I won't be able to review the PR until next week at the earliest, but I will try to get to it early next week.

[sobitneupane]

@paulnjs Could you please merge main?

[paulnjs]

@sobitneupane Kindly bump

[sobitneupane]

@paulnjs I can still reproduce the issue.

[paulnjs]

@sobitneupane Please help to check newest update

[sobitneupane]

@paulnjs I am still noticing two issues:

The number format changes after selection.

Screen.Recording.2026-07-16.at.12.09.01.mov

The selected number does not appear in the Attendees list in the background if a user was already selected.

[sobitneupane]

I think getDelegateAlternateText function might be redundant. Since the logic doesn't seem very complex, could we consider inlining it here instead of keeping a separate function? WDYT?

[paulnjs]

Good point, it's only used once. I updated it.

[paulnjs]

@sobitneupane I updated. Please help to check again. The lint error come from main, will try merge it again tmr

[sobitneupane]

@paulnjs Could you please merge main?

[paulnjs]

@sobitneupane I updated

[sobitneupane]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a93079b1e4

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[sobitneupane]

@paulnjs Could you please review above comments?

[sobitneupane]

@paulnjs When I set display Name for a phone number account, the phone number is shown instead of the display name.

Screen.Recording.2026-07-27.at.12.26.58.mov

[sobitneupane]

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

Screen.Recording.2026-07-27.at.12.11.01.mov

iOS: HybridApp

iOS: mWeb Safari

Screen.Recording.2026-07-27.at.12.31.01.mov

MacOS: Chrome / Safari

Screen.Recording.2026-07-27.at.11.49.27.mov

Screen.Recording.2026-07-27.at.11.53.28.mov

Screen.Recording.2026-07-27.at.12.26.58.mov

[paulnjs]

@sobitneupane Updated. Please check again.

[sobitneupane]

Reviewing the updates.

[sobitneupane]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 👍

Reviewed commit: 99ad4a8be5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[sobitneupane]

Screenshots/Videos

Android: HybridApp

https://github.com/user-attachments/assets/adcf2f3d-1bce-4037-9043-89aa1cabd538
https://github.com/user-attachments/assets/d72038f4-6703-4d8a-ae6d-6ef1ae3fb636

Android: mWeb Chrome

Screen.Recording.2026-08-06.at.14.32.04.mov

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-08-06.at.14.08.20.mov

Screen.Recording.2026-08-06.at.14.09.18.mov

Screen.Recording.2026-08-06.at.14.10.24.mov

[sobitneupane]

@paulnjs Could you please take a look at screen recording below? It seems there is still an issue with phone number with display names. After selecting a phone number, the corresponding display name is not appearing.

Screen.Recording.2026-08-06.at.14.36.53.mov

[paulnjs]

@sobitneupane I think the bug comes from main and was fixed. I merge main again and it's working well on my end. Could you please help to check again?

Screen.Recording.2026-08-07.at.11.20.35.mov

[sobitneupane]

@paulnjs I can still reproduce the issue on my end.

Screen.Recording.2026-08-07.at.15.43.24.mov