[$1000] URL appears as html in thread title and alternate text in search page

[kavimuru]

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

---

Action Performed:

1. Go to any chat
2. Send a website url
3. Hover and click on thread icon
4. See the header
5. Go to search and search "<a"

Expected Result:

Normal text should be shown

Actual Result:

URL shows in html format

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.26-1
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @Puneet-here
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686286858935369

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b674a204efbb9b04
• Upwork Job ID: 1671168762113949696
• Last Price Increase: 2023-06-20

[melvin-bot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[OSBotify]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @grgia (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[roryabraham]

@grgia is out for the weekend, going to grab this.

[roryabraham]

I confirmed that this bug is caused in the back-end. The root cause is that the text for the reportAction is being overwritten by HTML.

If you take these same actions offline, it will work.

[roryabraham]

That means that, if it's not too late, this should actually be a deploy blocker for the API, not E/App.

[roryabraham]

Going to create an internal deploy blocker

[roryabraham]

Internal issue link: https://github.com/Expensify/Expensify/issues/291036

[roryabraham]

PR to fix this ready here: https://github.com/Expensify/Web-Expensify/pull/37784

[roryabraham]

@grgia requested your review on that PR because this issue was auto-assigned to you originally 😉

[roryabraham]

This is fixed

[Puneet-here]

@roryabraham, is this eligible for the reporting compensation?

[Puneet-here]

@roryabraham, is this eligible for the reporting compensation?

cc: @johncschuster

[roryabraham]

Looks like @Puneet-here is eligible for the bug reporting bonus here.

[roryabraham]

Sorry I didn't notice it earlier, @Puneet-here

[Puneet-here]

No problem! Thanks for opening it again.

[roryabraham]

@johncschuster last TODO here is paying out the reporting bonus

[johncschuster]

Thanks for the callout, @roryabraham! I'll apply the External label now so the job can be created.

[melvin-bot]

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

[melvin-bot]

Current assignee @johncschuster is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

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

[johncschuster]

Sorry for the ping, @sobitneupane. I applied the label just to have the job get created automatically. Nothing to do here!

[johncschuster]

@Puneet-here I've just invited you to the job via Upwork. Can you ping me once you've accepted that?

[johncschuster]

@Puneet-here friendly bump so I can issue you the reporting bonus!

[Puneet-here]

Sorry for the delay. Just accepted the offer.

[johncschuster]

Thanks! I've just issued payment!

[Puneet-here]

Thanks. We can close the issue @johncschuster

[melvin-bot]

@johncschuster @roryabraham this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!