[HOLD for payment 2025-01-13] [$2000] When you long-press on a message, the message moves out of the screen frame and is hidden

[mvtglobally]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Navigate to any chat with multiple messages
2. Long press on the last message you sent

Expected Result:

When long pressing on the last message, we should adjust the scroll so that the message you just selected is visible.

Actual Result:

When you long-press on a message in iOS mobile, the message moves out of the screen frame and is hidden.

Workaround:

None

Platform:

Where is this issue occurring?

• iOS
• Android

Version Number: 1.1.92-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

RPReplay_Final1661747398.MP4

Expensify/Expensify Issue URL:
Issue reported by: @roryabraham
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1661612352759039

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @JmillsExpensify

[melvin-bot]

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

[melvin-bot]

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

[marcaaron]

User should be able to see which messages is being selected

What does this mean exactly... ? Looking at the video and I'm not even sure what the bug is.

[marcaaron]

When you long-press on a message in iOS mobile, the message moves out of the screen frame, and it’s not obvious which message you’ve selected

Also don't understand what is being proposed here.

[roryabraham]

The problem is that once the context menu pops up and the modal blur is applied, it's not clear which message you've long-pressed on. What I was imagining is that the message you selected would have a white background / be "immune" from the modal blur effect.

But I think a mockup would be very helpful here. @marcaaron suggested that we could use a "shimmer effect" as an alternative

[melvin-bot]

Triggered auto assignment to @michelle-thompson (Design), see these Stack Overflow questions for more details.

[michelle-thompson]

Hmm, what about when you hold down on a message the background highlights as grey like so?

[roryabraham]

Yeah, that works! We'll also need to make sure that we:

• Scroll the chat view so that the highlighted chat is visible despite the context menu opening
• Make sure we un-highlight the option when the context menu closes

[roryabraham]

Leaving you assigned so that you get the GH points @michelle-thompson

[melvin-bot]

Triggered auto assignment to @JmillsExpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[JmillsExpensify]

This has since moved to this PR: #42143

[hannojg]

After switching to the new arch we've encountered a bug in reanimated on the fabric renderer.
We are currently trying to solve it to move on with this issue:

Discussed here

[perunt]

Hey @shawnborton, I left a message here to clarify this PR. I look forward to your answer

[luacmartins]

Assigning myself to cover for Rory while he's on parental leave

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[luacmartins]

Damn, it's a shame that we reverted the PR 😞 @kirillzyusko let's work on v2 taking the blockers into consideration

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.80-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• fix: messages content overlap when bottom sheet is shown #42143

If no regressions arise, payment will be issued on 2025-01-13. 🎊

For reference, here are some details about the assignees on this issue:

• @terrysahaidak does not require payment (Contractor)
• @kirillzyusko does not require payment (Contractor)

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@terrysahaidak / @kirillzyusko] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@JmillsExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.