[Due for payment 2025-12-26] [$250] Members - User avatar changes after workspace invitation

[nlemma]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.2.67-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: N/A
Email or phone of affected tester (no customers): 76071
Issue reported by: Applause Internal Team
Device used: Windows 11, Chrome | iPhone SE 3rd generation, Tahoe 26.1, Chrome | Samsung A15, Android 15, Chrome
App Component: Workspace Settings

Action Performed:

1. Go to https://staging.new.expensify.com/ or open the app
2. Create a workspace
3. Go to the workspace > Members
4. Invite a non-existing user
5. Repeat step 4

Expected Result:

User avatar should remain unchanged after being invited to a workspace

Actual Result:

After a user is invited to a workspace, their avatar changes.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug7018151_1764640741610.explorer_QzfaikGmpP.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021998397531645517547
• Upwork Job ID: 1998397531645517547
• Last Price Increase: 2025-12-09

Issue Owner

Current Issue Owner: @sonialiap

[melvin-bot]

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.

[tsa321]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Members - User avatar changes after workspace invitation

What is the root cause of that problem?

There is a different hash function used to generate avatar in optimistic action when inviting new member which is getAccountIDHashBucket:

App/src/libs/UserAvatarUtils.ts

Line 54 in 032fdaf

function getAccountIDHashBucket({accountID = CONST.DEFAULT_NUMBER_ID, accountEmail, avatarURL}: DefaultAvatarArgsType): AvatarRange {

Meanwhile, the avatar on the Invite Confirmation Details page is generated using a different hash function, getAvatarForContact:

App/src/libs/RandomAvatarUtils.ts

Lines 59 to 63 in 4294b92

	const getAvatarForContact = (name?: string | null) => {
	if (!name) {
	return DEFAULT_AVATAR;
	}
	return avatars.at(StringUtils.hash(name, avatars.length)) ?? DEFAULT_AVATAR;

from:

App/src/components/ReportActionAvatars/useReportActionAvatars.ts

Line 128 in 4294b92

fallbackIcon: shouldUseCustomFallbackAvatar ? RandomAvatarUtils.getAvatarForContact(String(id)) : undefined,

Because these two functions produce different hash value, the resulting avatars will not match.

What changes do you think we should make in order to solve the problem?

we should use getAccountIDHashBucket to get hash value instead of StringUtils.hash which is used by getAvatarForContact and also check other places that use getAvatarForContact.

What alternative solutions did you explore? (Optional)

For more uniformity/consistency we could use utility functions in UserAvatarUtils for example getDefaultAvatar to get/generate avatar to replace the getAvatarForContact.

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.

[melvin-bot]

@sonialiap Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021998397531645517547

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @suneox (External)