[HOLD for payment 2023-04-27] LHN edited message UI shows the whole multiline message for a few seconds

[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. Send Any multiline code block message to chat
2. Observe the LHN list of the chat
3. Now edit the same multiline code block message
4. Observe the LHN

Expected Result:

LHN should show only the first line of the message

Actual Result:

It shows the whole message for a few seconds in LH

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.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

Recording.263.mp4

Expensify/Expensify Issue URL:
Issue reported by: @kerupuksambel
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1681820355045809

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b50c1ba8e6e2cc4f
• Upwork Job ID: 1651464466008215552
• Last Price Increase: 2023-04-27

[MelvinBot]

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

[MelvinBot]

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.

[MelvinBot]

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

[Pujan92]

Seems a regression from this PR

[francoisl]

Fix is being CPed to staging now.

[kerupuksambel]

Hi, sorry but it seems that this issue is pretty similar with what found here, that was reported first in the Slack conversation. https://expensify.slack.com/archives/C049HHMV9SM/p1681809609978589

[iwiznia]

Should I close this then? It is already being handled in #17212

[francoisl]

Hi, sorry but it seems that this issue is pretty similar with what found here, that was reported first in the Slack conversation. expensify.slack.com/archives/C049HHMV9SM/p1681809609978589

Yes it seems we need to change the "Issue reported by" for this issue @kavimuru, though I'm not sure about the exact procedure and if there's something else to to change too.

@iwiznia I'd say let's wait until the original issue and the fix are QA'ed on staging and then we can close.

[mountiny]

Thanks for handling this, I have update the issue body to mention @kerupuksambel as reported as they reported it first.

Confirmed that this is fixed in staging @sakluger could you please handle the $250 report bonus to @kerupuksambel for this and then we can close this

[MelvinBot]

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

[mountiny]

This is ready to pay the reporting bonus of $250

[sakluger]

I'm having a hell of a time creating a job manually in Upwork, it keeps returning errors. I'm going to apply the internal label to get the job created, then I'll fix everything from there.

[MelvinBot]

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

[MelvinBot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @mollfpr (Internal)

[sakluger]

@mollfpr, you can disregard, this issue is just for paying a reporting bonus and so I've unassigned you.

[sakluger]

@kerupuksambel I've sent you an offer through upwork.

[sakluger]

All paid 👍