Skip to content

[Due for payment 2026-01-27] [$250] Expense - Moved this report chat shown as html tag in search & member section #76717

Closed

Description

@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.71-5
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #67460
Email or phone of affected tester (no customers): dreamnitethedragon+726366363@gmail.com
Issue reported by: Applause Internal Team
Device used: Redminote 10S Android 13
App Component: Money Requests

Action Performed:

Pre-condition:
1.Account B has a default workspace and another workspace with bank account added
2.As account A set preference currency as USD and send a IOU to user B

  1. Launch app
  2. Open the IOU
  3. Tap pay dropdown and select workspace with bank account added
  4. Navigate to 1:1 chat
  5. Open the thread page for system message "moved this expense"
  6. Tap header - members
  7. Note header subtitle
  8. Navigate back twice and tap search icon
  9. Note the thread chat in search

Expected Result:

In members section, header subtitle must not show html tags.

In search, thread chat must not be shown as html tags.

Actual Result:

In members section, header subtitle shows html tags.

In search, thread chat is shown as html tags.

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

Bug7020520_1764852110407.Screenrecorder-2025-12-04-18-11-11-53.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021996767194806750226
  • Upwork Job ID: 1996767194806750226
  • Last Price Increase: 2025-12-12
  • Automatic offers:
    • daledah | Contributor | 109801388
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @jliexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 4, 2025
  2. melvin-bot commented on Dec 4, 2025

    @melvin-bot

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

  3. daledah commented on Dec 4, 2025

    @daledah
    Contributor

    Proposal

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

    In members section, header subtitle shows html tags.

    What is the root cause of that problem?

    We don't parser html to text here

    subtitle={StringUtils.lineBreaksToSpaces(getReportName(report))}

    const styledRecentReports = recentReportsOptions.map((item) => ({
    ...item,
    pressableStyle: styles.br2,
    text: StringUtils.lineBreaksToSpaces(item.text),
    wrapperStyle: [styles.pr3, styles.pl3],
    }));

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

    We should add Parser.htmlToText to wrap this subtitle like we did here

        subtitle={StringUtils.lineBreaksToSpaces(Parser.htmlToText(getReportName(report)))}
    

    subtitle={StringUtils.lineBreaksToSpaces(getReportName(report))}

        text: StringUtils.lineBreaksToSpaces(Parser.htmlToText(item.text)),
    

    const styledRecentReports = recentReportsOptions.map((item) => ({
    ...item,
    pressableStyle: styles.br2,
    text: StringUtils.lineBreaksToSpaces(item.text),
    wrapperStyle: [styles.pr3, styles.pl3],
    }));

    Optional: we can also add the parser here

    Note: We can also add a condition that the report action name must be different from add comment before we parse it.”

    What alternative solutions did you explore? (Optional)

    NA

    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.

  4. mkzie2 commented on Dec 4, 2025

    @mkzie2
    Contributor

    Proposal

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

    In members section, header subtitle shows html tags.

    What is the root cause of that problem?

    We are using the report name from getReportName to display in RoomMemberPage

    subtitle={StringUtils.lineBreaksToSpaces(getReportName(report))}

    In SearchAutocompleteList

    const additionalSections = useMemo(() => {
    return getAdditionalSections?.(searchOptions);
    }, [getAdditionalSections, searchOptions]);

    result.text = reportName;

    In this case, the reportName contains the html tag

    We also can reproduce the issue in other place like HeaderView or SearchRouterQuery, …

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

    To fix this issue totally, we should fix it in getReportName, because in this function we will return the parsed name like we did in this line

    Update

    return attributes[report.reportID].reportName;

    To

           return Parser.htmlToText(attributes[report.reportID].reportName);
    

    What alternative solutions did you explore? (Optional)

    We can consider to add Parser.htmlToText in ReportNameUtils.getReportName, then use it instead of ReportUtils.getReportName

    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.

  5. kadiealexander commented on Dec 5, 2025

    @kadiealexander
    Contributor

    Android <> iOS bug swap

  6. jliexpensify commented on Dec 5, 2025

    @jliexpensify
    Contributor

    Not the same HTML issues here as well: #76047

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Dec 5, 2025
  8. melvin-bot commented on Dec 5, 2025

    @melvin-bot
  9. changed the title [-]Expense - Moved this report chat shown as html tag in search & member section[/-] [+][$250] Expense - Moved this report chat shown as html tag in search & member section[/+] on Dec 5, 2025
  10. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Dec 5, 2025
  11. 68 remaining items

  12. changed the title [-][$250] Expense - Moved this report chat shown as html tag in search & member section[/-] [+][Due for payment 2026-01-27] [$250] Expense - Moved this report chat shown as html tag in search & member section[/+] on Jan 20, 2026
  13. melvin-bot commented on Jan 20, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.4-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-01-27. 🎊

    For reference, here are some details about the assignees on this issue:

  14. melvin-bot commented on Jan 20, 2026

    @melvin-bot

    @ZhenjaHorbach @jliexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  15. jliexpensify commented on Jan 27, 2026

    @jliexpensify
    Contributor

    Bump @ZhenjaHorbach for the checklist please

  16. ZhenjaHorbach commented on Jan 27, 2026

    @ZhenjaHorbach
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

    Unfortunately, I did not find a suitable PR

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: NA

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal

    Pre-condition:

    • Account B has a default workspace and another workspace with bank account added
    • As account A set preference currency as USD and send a IOU to user B

    Test:

    1. Launch app
    2. Open the IOU
    3. Tap pay dropdown and select workspace with bank account added
    4. Navigate to 1:1 chat
    5. Open the thread page for system message "moved this expense"
    6. Tap header - members
    7. Note header subtitle
    8. Navigate back twice and tap search icon
    9. Note the thread chat in search
    10. Verify that: In members section, header subtitle must not show html tags.
    11. Verify that: In search, thread chat must not be shown as html tags.

    Do we agree 👍 or 👎

  17. ZhenjaHorbach commented on Jan 27, 2026

    @ZhenjaHorbach
    Contributor

    @jliexpensify
    Sorry for delay
    Done!

  18. jliexpensify commented on Jan 27, 2026

    @jliexpensify
    Contributor

    Payment Summary

    NEW Upwork job

  19. jliexpensify commented on Jan 27, 2026

    @jliexpensify
    Contributor

    @daledah - the old job closed and I have no way to pay you out. Please accept this new job: https://www.upwork.com/jobs/~022016078113665621561

  20. daledah commented on Jan 27, 2026

    @daledah
    Contributor

    @jliexpensify i accepted

  21. garrettmknight commented on Jan 27, 2026

    @garrettmknight
    Contributor

    $250 approved for @ZhenjaHorbach

  22. jliexpensify commented on Jan 27, 2026

    @jliexpensify
    Contributor

    Paid and job closed!

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions