[HOLD for payment 2023-06-29] [$1000] If you press and hold on a message and then release the press, the hover effect will be lost

[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. Open the app
2. Open any chat
3. Press and hold on message sender name
4. Release it the press below the name

Expected Result:

The message hover effect should not be lost: the menu (of emojis, copy / mark unread / edit) should be displayed

Actual Result:

The message hover effect is lost: the menu (of emojis, copy / mark unread / edit) stops showing up

Workaround:

unknown

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.2.89-0
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
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:

Screen.Recording.2023-03-25.at.7.12.09.AM.mov

Screen.Recording.2023-04-03.at.4.25.09.AM.mov

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit

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

[MelvinBot]

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

[MelvinBot]

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

[MelvinBot]

@laurenreidexpensify Eep! 4 days overdue now. Issues have feelings too...

[laurenreidexpensify]

Apols for delay in reviewing this. Asking for a better video in the thread - I'm struggling to follow repro steps / identify the bug based on current evidence. Thanks

[laurenreidexpensify]

Asking here https://expensify.slack.com/archives/C01SKUP7QR0/p1680523338384019 for some more background

[laurenreidexpensify]

@Beamanator confirmed he can reproduce, have updated the O/P with a touch more detail