[HOLD for payment 2025-01-15] mWeb/Safari - Chat - New message button appears in the chat for the messages sender

[IuliiaHerets]

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

---

Version Number: 9.0.78-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/cases/view/2950407
Issue reported by: Applause Internal Team
Device used: iPhone 15 iOS 18.1.1 Safari
App Component: Chat Report View

Action Performed:

1. Navigate to staging.new.expensify.com and log in as a gmail user
2. Create a new chat with the other user
3. Send 3 images (or 20+ messages) to the chat so the top of the conversation is hidden
4. Scroll to the top of the chat

Expected Result:

New message button does not appear for the sender of messages

Actual Result:

New message button appears in the chat for the messages sender. After tapping on it the conversation scrolls to the bottom, but no "New message" marker is shown
Issue happens only on mWeb/Safari.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6701558_1735001004269.New_message_for_sender.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @anmurali

[melvin-bot]

Triggered auto assignment to @youssef-lr (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

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

[jasperhuangg]

Pretty minor visual bug, I don't think we need to block deploy on this.