[$500] LHN reflects wrong hint when user sents message after an attachment

[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:

step 1: open workspace from user A
step 2: add user B to the work space
step 3: send attachment from user A
step 4: send message from user B
step 5: observe LHN tab hint from user A

Expected Result: LHN tab hint shows the message

Actual Result: LHN tab hint shows attachment

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.65-5
Reproducible in staging?: y
Reproducible in production?: y
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

admin.LHN.hint.gets.wrong.when.user.sends.message.after.admin.sennt.attachment.mp4

Recording.1565.mp4

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0163d7b176bbb6f038
• Upwork Job ID: 1715323614227767296
• Last Price Increase: 2023-12-08

[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

[jscardona12]

It is reproducible on lastest main

[allroundexperts]

This should be fixed from the backend. The pusher is not sending the updated lastMessageTranslationKey for the report.

[allroundexperts]

We can also solve this by removing this but I think we should fix it from the backend.

[s-alves10]

This would be fixed by this PR
I think we can hold this issue

[melvin-bot]

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

[melvin-bot]

@johncschuster Whoops! This issue is 2 days overdue. Let's get this updated quick!

[johncschuster]

@allroundexperts do you agree with this?

This would be fixed by this PR
I think we can hold this issue

[melvin-bot]

@johncschuster Huh... This is 4 days overdue. Who can take care of this?

[johncschuster]

Putting this on hold while we wait for https://github.com/Expensify/App/pull/26850/files

[johncschuster]

Ok! It looks like #26850 has been deployed to prod. @kavimuru / @lidiyakelay can you check to see if this behavior persists?

[johncschuster]

bump @kavimuru / @lidiyakelay

[johncschuster]

bump @kavimuru / @lidiyakelay

[lidiyakelay]

@johncschuster SORRY!! for the late reply. This issue doesn't seem to be occurring anymore.

Lhn_GITHUB.mp4

[lidiyakelay]

@johncschuster but this seems to be still occurring on mobile app

[lidiyakelay]

bump @johncschuster

[s77rt]

@johncschuster Let's close this

[s77rt]

@johncschuster ^

[mvtglobally]

Issue not reproducible during KI retests. (Fourth week). Are we good to close?

[melvin-bot]

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

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[s77rt]

@johncschuster This can be closed

[melvin-bot]

@johncschuster, @s77rt Whoops! This issue is 2 days overdue. Let's get this updated quick!

[s77rt]

@johncschuster ^

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[s77rt]

Not overdue. To be closed

[s77rt]

To be closed ^

[mvtglobally]

Issue not reproducible during KI retests. (Fifth week)

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@johncschuster, @s77rt Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@johncschuster, @s77rt Huh... This is 4 days overdue. Who can take care of this?

[johncschuster]

Looks like we can close this one. Thanks, everyone!