Skip to content

Migrate User Avatar usages - #98031

Merged
roryabraham merged 14 commits into
Expensify:mainfrom
software-mansion-labs:chore/migrate-avatar-user-avatar-cases
Aug 25, 2026
Merged

roryabraham merged 14 commits into
Expensify:mainfrom
software-mansion-labs:chore/migrate-avatar-user-avatar-cases

Conversation

@jmusial

@jmusial jmusial commented Aug 7, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

This PR migrates raw Avatar call sites across 33 files to the UserAvatar (or Icon or AccountAvatar if the case calls for it).

This removes duplicated avatar-resolution logic and per-site Onyx lookups and ensures consistent fallback and tooltip behaviour everywhere a single account's avatar is rendered.

Some Avatar uses are left un migrated - this depend on dynamic icons and can be either User or Avatar

Fixed Issues

$ #95600
PROPOSAL:

Tests

  1. Open the app.
  2. Verify the sidebar profile avatar shows your avatar.
  3. Open a chat, type @ in the composer
  4. Verify each suggestion shows a round user avatar and the @here row shows a green megaphone icon.
  5. Create a task in that chat and assign it to another member.
  6. Verify the task preview shows the assignee's avatar on the left, and on web hovering it shows their name tooltip.
  7. Navigate to Account -> Profile.
  8. Verify the large preview avatar renders.
  9. Go to Workspaces -> Your workspace -> Members and open a member.
  10. Verify the member's large avatar renders at the top of the detail page.

Offline tests

QA Steps

Same as tests.

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 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 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)
  • 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)
  • 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.
  • 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-08-18.at.14.30.42.mov
Android: mWeb Chrome
Screen.Recording.2026-08-18.at.14.30.42.mov
iOS: Native
Screen.Recording.2026-08-18.at.14.28.38.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-08-18.at.14.13.17.mov

@codecov

codecov Bot commented Aug 7, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/components/AccountSwitcher.tsx 82.00% <100.00%> (-0.36%) ⬇️
src/components/Avatar/index.tsx 100.00% <ø> (ø)
src/components/AvatarSelector.tsx 100.00% <ø> (ø)
src/components/BookCallButton.tsx 100.00% <100.00%> (ø)
src/components/MenuItem/MenuItem.tsx 91.85% <ø> (ø)
...ts/Search/SearchList/ListItem/ExportedIconCell.tsx 65.51% <100.00%> (+1.88%) ⬆️
...earch/SearchList/ListItem/MemberListItemHeader.tsx 0.00% <ø> (ø)
...nts/Search/SearchList/ListItem/TaskListItemRow.tsx 0.00% <ø> (ø)
...onents/Search/SearchList/ListItem/UserInfoCell.tsx 90.90% <100.00%> (-0.76%) ⬇️
...components/SelectionList/ListItem/CardListItem.tsx 0.00% <ø> (ø)
... and 21 more
... and 12 files with indirect coverage changes

@jmusial

jmusial commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 05ef70312c

ℹ️ 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".

@jmusial

jmusial commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6657970111

ℹ️ 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".

@jmusial

jmusial commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b535919c94

ℹ️ 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".

@jmusial
jmusial marked this pull request as ready for review August 19, 2026 10:44
@jmusial
jmusial requested review from a team as code owners August 19, 2026 10:44
@melvin-bot
melvin-bot Bot requested a review from mananjadhav August 19, 2026 10:44
@melvin-bot

melvin-bot Bot commented Aug 19, 2026

Copy link
Copy Markdown

@mananjadhav 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]

@melvin-bot
melvin-bot Bot requested review from trjExpensify and removed request for a team August 19, 2026 10:44
@trjExpensify
trjExpensify removed their request for review August 20, 2026 18:50
@trjExpensify

Copy link
Copy Markdown
Contributor

PR doesn’t need product input as a refactor PR. Unassigning and unsubscribing myself.

@mananjadhav

Copy link
Copy Markdown
Collaborator

Reviewing the PR.

@mananjadhav mananjadhav left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few comments.

@jmusial

jmusial commented Aug 21, 2026

Copy link
Copy Markdown
Contributor Author

@mananjadhav thx for a good review 😄 Addressed all.


const subscriptionLink = subscriptionPlan ? `${environmentURL}/${ROUTES.SETTINGS_SUBSCRIPTION.getRoute(Navigation.getActiveRoute())}` : CONST.PLAN_TYPES_AND_PRICING_HELP_URL;

const iconSize = isIllustration ? 48 : StyleUtils.getAvatarSize(CONST.AVATAR_SIZE.DEFAULT);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Can we replace the magic number with some const please?

@mananjadhav mananjadhav left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One final comment. Starting to test.

@mananjadhav

mananjadhav commented Aug 23, 2026 •

Copy link
Copy Markdown
Collaborator

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • 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 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
mweb-android-avatar.mov
iOS: HybridApp
ios-avatar.mov
iOS: mWeb Safari
mweb-safari-avatar.mov
MacOS: Chrome / Safari
web-user-avatar.mov

@mananjadhav

Copy link
Copy Markdown
Collaborator

Tested web, still checking other platforms once.

@jmusial

jmusial commented Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

@mananjadhav kind bump

@mananjadhav

Copy link
Copy Markdown
Collaborator

Apologies I had to take up a deploy issue. Back to testing this.

@melvin-bot
melvin-bot Bot requested a review from roryabraham August 25, 2026 18:28
@mananjadhav

Copy link
Copy Markdown
Collaborator

Checklist here #98031 (comment)

}
}

const integrationIcons = [

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NAB for now: I don't think that we should use static arrays and .map for rendering like this. A few reasons:

  • It will be more tempting for future authors to add a configuration prop to the thing rendered in the .map callback to handle a different variant of the thing in the array.
  • React Compiler won't memoize it as granularly. I think the whole .map callback will be memoized as one function, rather than granularly memoizing all the JSX nodes.
  • It doesn't have that much of a readability boost over JSX.
  • The guidelines say not to do it this way

Not going to block on this, but @jmusial we should address this in a fast-follower.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MelvinBot create an issue for this. Label it Daily, assign to jmusial and roryabraham.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@roryabraham
roryabraham merged commit efedb13 into Expensify:main Aug 25, 2026
37 of 39 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 roryabraham has triggered a test Expensify/App build. You can view the workflow run here.

@MelvinBot

Copy link
Copy Markdown
Contributor

Created a follow-up issue for the remaining un-migrated Avatar usages (the dynamic-icons cases this PR intentionally left in place): #99461

  • Label: Daily
  • Assignees: jmusial, roryabraham

view run

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.4.61-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

Copy link
Copy Markdown
Contributor

Help site review — no changes required

I reviewed the changes in this PR against the help site articles under App/docs/articles and no documentation updates are needed.

This PR is a purely internal component refactor: it migrates raw Avatar call sites to UserAvatar (or Icon/AccountAvatar), removing duplicated avatar-resolution logic and per-site Onyx lookups. It does not introduce, rename, or change any user-facing feature, flow, tab, setting, or button label — avatars render the same as before, just with consistent fallback and tooltip behavior. The help site documents user-facing behavior and UI, none of which changes here.

No draft PR was created since there is nothing to document.

jmusial, if you believe a specific user-facing behavior did change and should be documented, let me know which flow and I'll draft the help site update.


view run

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.4.61-4 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants