[Due for payment 2025-04-07] [$250] Room - Chat not autoscrolled, when system message appears after mentioning two users.

[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.1.11-1
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?/tests/view/5724879&group_by=cases:section_id&group_order=asc&group_id=296763
Email or phone of affected tester (no customers): ibellicotest+284@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome
App Component: Chat Report View

Action Performed:

1. Open the staging.new.expensify.com website.
2. Tap on the FAB and select "Start Chat"
3. Tap on "Room" and complete the creation flow.
4. Once redirected to the new room, mention two users that are not part of it.
5. Send the mentions to chat and wait for the system message to invite the users to be received.
6. Check if chat is correctly autoscrolled when system message appears.

Expected Result:

When system message to invite new members is displayed, chat should be automatically scrolled to the bottom.

Actual Result:

Chat is not autoscrolled to the bottom, when system message to invite the two mentioned users appears.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6767046_1741677535983.System.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021899470389407388503
• Upwork Job ID: 1899470389407388503
• Last Price Increase: 2025-03-18
• Automatic offers:
• daledah | Contributor | 106582272

Issue Owner

Current Issue Owner: @johncschuster

[melvin-bot]

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

[melvin-bot]

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