LHN - Status emoji is not shown next to account name

[lanitochka17]

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

---

Issue found when executing PR #24414

Action Performed:

1. Open https://staging.new.expensify.com/
2. Log in using Account A.
3. Click on Settings.
4. Click on Profile.
5. Click on Status.
6. Click on Status again and select an emoji and enter a text.
7. Click on Save.
8. Make sure the chosen emoji appears next to avatar.
9. Log out of Account A.
10. Log in using Account B.
11. Look for the chat with Account A in LHN.

Expected Result:

Account B should see Account A's status emoji next to their name

Actual Result:

There is no Account A's status emoji next to their name

Workaround:

Unknown

Platforms:

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

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

Version Number: 1.3.58-0

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

bandicam.2023-08-28.16-07-05-708.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

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

[procrastagonist]

Works as expected on my side

[garrettmknight]

@stitesExpensify can you test this one and see if it's still happening on the beta?

[stitesExpensify]

Hmm looks like it could be something to do with having a long display name vs a long email? I'll add it to the project

[stitesExpensify]

cc @perunt