[Due for payment 2025-12-23] [$250] Search - Profile name change not reflected instantly in search results

[jponikarchuk]

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.49-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1892/folder/13176964/41237771/1005353097
Email or phone of affected tester (no customers): Slottwo1@gmail.com
Issue reported by: Applause Internal Team
Device used: Redminote 10s android 13 phone
App Component: Search

Action Performed:

1. Launch app
2. Login with new gmail account
3. Tap workspace - create a workspace
4. Go to inbox
5. Tap search
6. Enter "you"
7. Note self DM is shown in search results
8. Go to profile - change display name
9. Go to inbox
10. Tap search
11. Enter "you"
12. Note search results are not shown
13. Go to troubleshoot - clear cache
14. Go to inbox - search
15. Enter " you"
16. Note self dm is not shown in results
17. Search entering new profile with its starting letters
18. Search "you" again
19. Note now self DM is shown in results

Expected Result:

Profile name change should be reflected immediately in search so that results appear without needing to search using the new name first.

Actual Result:

After changing the profile display name, searching “you” doesn’t show results because the updated profile name isn’t reflected instantly in search. Self DM itself works fine — only the display name update delay causes it to not appear.

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

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021991093433782404694
• Upwork Job ID: 1991093433782404694
• Last Price Increase: 2025-11-26

Issue Owner

Current Issue Owner: @eh2077

[melvin-bot]

Triggered auto assignment to @dylanexpensify (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.

[dmkt9]

Proposal

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

After changing the profile display name, searching “you” doesn’t show results because the updated profile name isn’t reflected instantly in search. Self DM itself works fine — only the display name update delay causes it to not appear.

What is the root cause of that problem?

When updating the display name, the reportName of the report option item doesn’t automatically include the "(you)" postfix. It only gets added after performing a search in the search route and the option item is refreshed.

App/src/libs/OptionsListUtils/index.ts

Line 911 in c51a657

reportName = showPersonalDetails ? getDisplayNameForParticipant({accountID: accountIDs.at(0)}) || formatPhoneNumber(personalDetail?.login ?? '') : getReportName(report);

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

If the report is a selfDM chat, we should append the "(you)" postfix to its reportName.

App/src/libs/OptionsListUtils/index.ts

Line 911 in c51a657

reportName = showPersonalDetails ? getDisplayNameForParticipant({accountID: accountIDs.at(0)}) || formatPhoneNumber(personalDetail?.login ?? '') : getReportName(report);

        reportName = showPersonalDetails
            ? getDisplayNameForParticipant({accountID: accountIDs.at(0), shouldAddCurrentUserPostfix: isSelfDM(report)}) || formatPhoneNumber(personalDetail?.login ?? '')
            : getReportName(report);

What alternative solutions did you explore? (Optional)

N/A

[lorretheboy]

Proposal

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

After changing the profile display name, searching “you” doesn’t show results because the updated profile name isn’t reflected instantly in search. Self DM itself works fine — only the display name update delay causes it to not appear.

What is the root cause of that problem?

When creating search options for reports with showPersonalDetails: true (which is used for self DM reports), the function was calling getDisplayNameForParticipant without passing the personalDetailsData parameter.

This caused getDisplayNameForParticipant to use its default parameter value, which is the module-level allPersonalDetails variable from ReportUtils.ts. While this variable is connected to Onyx and should update when personal details change, there's a timing issue where the search options are regenerated in OptionListContextProvider with the updated personal details, but getDisplayNameForParticipant was still using the cached module-level data instead of the fresh data passed to createOption.

App/src/libs/OptionsListUtils/index.ts

Lines 910 to 917 in 36a1a88

	result.alternateText =
	showPersonalDetails && personalDetail?.login
	? personalDetail.login
	: getAlternateText(result, {showChatPreviewLine, forcePolicyNamePreview}, !!result.private_isArchived, lastActorDetails);
	reportName = showPersonalDetails ? getDisplayNameForParticipant({accountID: accountIDs.at(0)}) || formatPhoneNumber(personalDetail?.login ?? '') : getReportName(report);
	} else {
	// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
	reportName = getDisplayNameForParticipant({accountID: accountIDs.at(0)}) || formatPhoneNumber(personalDetail?.login ?? '');

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

We should pass the personalDetails parameter to getDisplayNameForParticipant so it uses the updated personal details data that was passed to createOption function.

        reportName = showPersonalDetails ? getDisplayNameForParticipant({accountID: accountIDs.at(0), personalDetailsData: personalDetails ?? undefined}) || formatPhoneNumber(personalDetail?.login ?? '') : getReportName(report);
    } else {
        // eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
        reportName = getDisplayNameForParticipant({accountID: accountIDs.at(0), personalDetailsData: personalDetails ?? undefined}) || formatPhoneNumber(personalDetail?.login ?? '');

Note: We can add shouldAddCurrentUserPostfix param as well if needed (by checking isSelfDM)

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.

[melvin-bot]

@dylanexpensify 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/~021991093433782404694

[melvin-bot]

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