Group - Group chat header hidden; tap shows empty name while preview…

[whiletrace]

… shows saved name

Group - Group chat header hidden; tap shows empty name while preview…

Explanation of Change

Creates a conditional prop shouldParseHtml that is passed to and used by the DisplayNames component. This prop is set to true for all cases except when isGroupChat is true, ensuring HTML is not parsed for group chat titles. This behavior is also applied in ReportDetails via rawReportName and reportNameForMessages, which allow a check against isGroupChat to conditionally disable HTML parsing for group chats while allowing it for all other report types

Fixed Issues

$ #68721 (comment)
PROPOSAL: #68721 (comment)

Tests

Launch app
2 click actions button on left of screen marked +
select create chat from the menu
in the form field that appears enter a user name, email, or phone
matching user will appear below form field
click button right side of the user entry which will be labeled add to group
on bottom Left of screen click green button labeled next
Click on Group Name
Delete previous entry
Enter < > as the group name
Click Save
note preview contains the saved group name < >
Click Create group
Note Header will have New Group name < >
Click Header
Note detail will show group name: < >-
[x] Verify that no errors appear in the JS console

Offline tests

Launch app
2 click actions button on left of screen marked +
select create chat from the menu
in the form field that appears enter a user name, email, or phone
matching user will appear below form field
click button right side of the user entry which will be labeled add to group
on bottom Left of screen click green button labeled next
Click on Group Name
Delete previous entry
Enter < > as the group name
Click Save
note preview contains the saved group name < >
Click Create group
Note Header will have New Group name < >
Click Header
Note detail will show group name: < >### QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
Same as tests

• 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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • 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

<img width="1206" height="2622" alt="safariweb" src="https://github.com/user-attachments/assets/86b4f23f-8af3-4317-badc-f90d40f

c04cb" />

MacOS: Chrome / Safari

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
src/pages/ReportDetailsPage.tsx	59.59% <100.00%> (ø)
src/pages/home/HeaderView.tsx	81.81% <100.00%> (+0.12%)	⬆️
... and 5 files with indirect coverage changes

[whiletrace]

There was an error that I caught in both IOS and Android standalone. Not related to this PR, I was able to reproduce in Main branch. When in a group chat and user clicks to choose an emoji add to message this error is displayed.

[melvin-bot]

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

[joekaufmanexpensify]

Good from a product perspective 👍

[whiletrace]

@QichenZhu update I will have requested changes finished and ready 12/3/2025 just need to update testfile with requested changes.

[whiletrace]

update
ready for review, need to refactor the deprecations that just popped up

[whiletrace]

@whiletrace please merge main into this PR to get rid of the lint errors. the errors are still not fixed on main.
oka

339:27  error    `getReportName` is deprecated. Moved to src/libs/ReportNameUtils.ts.
Use ReportNameUtils.computeReportName for full name generation.
For reading a stored name only, use ReportNameUtils.getReportName                                                                                            @typescript-eslint/no-deprecated

/home/runner/work/App/App/src/pages/home/HeaderView.tsx
  149:19  error  `getReportName` is deprecated. Moved to src/libs/ReportNameUtils.ts.
Use ReportNameUtils.computeReportName for full name generation.
For reading a stored name only, use ReportNameUtils.getReportName  @typescript-eslint/no-deprecated

✖ 4 problems (2 errors, 2 warnings)

okay this can hold till tomorrow.

[whiletrace]

update
I am currently at a Blocker, concerning the deprecation of getReportNames and the new implementation, currently tests are failing, I am asking the wider community for clarification that can be found here

[QichenZhu]

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
  https://expensify.slack.com/archives/C049HHMV9SM/p1764642854883869
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I verified proper code patterns were followed (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 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)
• 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
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • 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
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • 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 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 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.
• 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

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2025-12-10.at.6.17.22.PM.mov

[QichenZhu]

This PR fixes the original issue well.

It also works correctly in several potential regression scenarios:

1. Delayed submission

2. Auto paid

3. Auto forwarded

4. Changed approver

5. Moved action

6. Auto approval

7. Sync failed

[whiletrace]

update I am currently at a Blocker, concerning the deprecation of getReportNames and the new implementation, currently tests are failing, I am asking the wider community for clarification that can be found here

@QichenZhu if you have any insights on this It would be much appreciated.I tried to find some documentation and reached out in slack ,so for no reply. Is this even my problem to find a solution to or am I supposed to wait for a fix to be merged into main? This is the issue that is blocking us from moving forward.

import {getReportName} from "@libs/ReportNameUtils";

import reportAttributes from "@userActions/OnyxDerived/configs/reportAttributes";

const title = getReportName(report, reportAttributes);

this matches the patterns mentioned in the original PR using the derived value to the get the names, however a test is failing for the component: the test is receiving a random string when it is expecting 'test'.

[whiletrace]

unblocked the eslint deprecated warnings by using // eslint-disable-next-line @typescript-eslint/no-deprecated confident this is the right solution, was implemented in ReportDetails.tsx in a previous PR for exactly the same issue, followed same pattern.

[QichenZhu]

Still looks good.

[whiletrace]

🤞

[OSBotify]

✋ 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]

🚀 Deployed to staging by https://github.com/carlosmiceli in version: 9.2.75-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	cancelled 🔪

[OSBotify]

🚀 Deployed to staging by https://github.com/carlosmiceli in version: 9.2.75-0 🚀

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

[IuliiaHerets]

@whiletrace QA team notice that "Hidden" is still shown in the LHN for Web and iOS. So we fail this PR with an original issue

1765418275428.75988-Web.mp4

[QichenZhu]

@IuliiaHerets this PR is very conservative and only fixes the original issue which doesn't mention LHN (see OP). We are aware of the LHN issue and fixed it before, but it caused regressions and was reverted, so we need to keep the changes minimal this time.

[IuliiaHerets]

@QichenZhu in this case we need to create a new issue, right?

[whiletrace]

@IuliiaHerets what would make sense here that since the LHN was out of scope of the original issue , and this PR addresses the specific use case described in the original issue. We pass this PR and create a new issue for the the LHN display , at which time as this PR deploys to production I can submit a proposal to fix the LHN issue properly.

[IuliiaHerets]

@whiletrace logged a new issue

[OSBotify]

🚀 Deployed to staging by https://github.com/carlosmiceli in version: 9.2.77-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	cancelled 🔪
🍎 iOS 🍎	cancelled 🔪

[OSBotify]

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.2.77-1 🚀

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

[whiletrace]

@IuliiaHerets this PR is very conservative and only fixes the original issue which doesn't mention LHN (see OP). We are aware of the LHN issue and fixed it before, but it caused regressions and was reverted, so we need to keep the changes minimal this time.

@QichenZhu thanks for your support