[Due for payment 2025-09-19] [$250] mWeb - Chat - Chat doesn't auto-scroll when a payment is received with chat opened

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.78-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

Precondition: Log in with two different accounts (User A,User B)

Go to the testing website https://staging.new.expensify.com/
User A: Open a chat with User B
User A: Send some messages to make the chat scrollable
User B, Open a chat with User A
User B, Tap on the "+" button
User B, Select "Pay User A" option
User B, Complete the payment flow and submit it.

Expected Result:

User A verifies that the expense appears in the chat and the chat is scrolled to the bottom

Actual Result:

User A verifies that the chat doesn't auto-scroll when a payment is received, and the payment preview isn't visible without manually scrolling down

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

Platforms Tested:

On which of our officially supported platforms was this issue tested:

Screenshots/Videos

Add any screenshot/video evidence

Bug6868942_1750805996901.User_A.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021970190044341975545
Upwork Job ID: 1970190044341975545
Last Price Increase: 2025-09-22

@garrettmknight

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

Proposal

Please re-state the problem that we are trying to solve in this issue.

User A verifies that the chat doesn't auto-scroll when a payment is received, and the payment preview isn't visible without manually scrolling down

What is the root cause of that problem?

Currently only implements the scrollToBottom mechanism when an action is removed but not added:

App/src/pages/home/report/ReportActionsList.tsx

Lines 347 to 355 in 15c2eb6

    
           if ( 
        
               scrollingVerticalOffset.current < AUTOSCROLL_TO_TOP_THRESHOLD && 
        
               previousLastIndex.current !== lastActionIndex && 
        
               reportActionSize.current > sortedVisibleReportActions.length && 
        
               hasNewestReportAction 
        
           ) { 
        
               setIsFloatingMessageCounterVisible(false); 
        
               reportScrollManager.scrollToBottom(); 
        
           }

What changes do you think we should make in order to solve the problem?

Add scrollToBottom mechanism when detecting a new action added:

App/src/pages/home/report/ReportActionsList.tsx

Lines 347 to 352 in 15c2eb6

    
           if ( 
        
               scrollingVerticalOffset.current < AUTOSCROLL_TO_TOP_THRESHOLD && 
        
               previousLastIndex.current !== lastActionIndex && 
        
               reportActionSize.current > sortedVisibleReportActions.length && 
        
               hasNewestReportAction 
        
           ) {

if (
    scrollingVerticalOffset.current < AUTOSCROLL_TO_TOP_THRESHOLD &&
    previousLastIndex.current !== lastActionIndex &&
    reportActionSize.current !== sortedVisibleReportActions.length &&
    hasNewestReportAction
) {

If we only want scrollToBottom with the same account, we will add the check const isFromCurrentUser = lastAction?.childLastActorAccountID ?? lastAction?.childOwnerAccountID ?? CONST.REPORT.OWNER_ACCOUNT_ID_FAKE === currentUserAccountID
If we only want to handle the IOU case, we can add a condition to the if clause.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

NA

What alternative solutions did you explore? (Optional)

NA

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

Job added to Upwork: https://www.upwork.com/jobs/~021943737232871320803

@c3024

Triggered auto assignment to Contributor-plus team member for initial proposal review - @c3024 (External)

@c3024

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

Will update today.

@dmkt9

📣 @dmkt9 You have been assigned to this job!
Please apply to the Upwork job and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Once you apply to this job, your Upwork ID will be stored and you will be automatically hired for future jobs!
Keep in mind: Code of Conduct | Contributing 📖

@dmkt9

@dmkt9 please apply!

@garrettmknight

@garrettmknight Thanks. I have just applied for the job.

Offer is out

@DylanDylann

@DylanDylann checklist please.

BugZero Checklist:

[Contributor] Classify the bug: Looks like this is a new requirement

Bug classification

Source of bug:

1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:

Where bug was reported:

2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:

Who reported the bug:

[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

Link to comment: Looks like this is a new requirement
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

Link to issue:

Regression Test Proposal

Precondition: Log in with two different accounts (User A,User B)

Test:

Go to the testing website https://staging.new.expensify.com/
User A: Open a chat with User B
User A: Send some messages to make the chat scrollable
User A: Scroll down to the bottom of the conversation
User B, Open a chat with User A
User B, Tap on the "+" button
User B, Select "Pay User A" option
User B, Complete the payment flow and submit it.
User A verifies that the expense appears in the chat and the chat is scrolled to the bottom

Do we agree 👍 or 👎

@dmkt9

Payment Summary

Contributor: @dmkt9 paid $250 via Upwork
Contributor+: @DylanDylann due $250 via NewDot

@DylanDylann

$250 approved for @DylanDylann

Navigation Menu

Repository navigation

[Due for payment 2025-09-19] [$250] mWeb - Chat - Chat doesn't auto-scroll when a payment is received with chat opened #65792

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

98 remaining items

BugZero Checklist:

Regression Test Proposal

Precondition: Log in with two different accounts (User A,User B)

Test:

Payment Summary

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	if (
	scrollingVerticalOffset.current < AUTOSCROLL_TO_TOP_THRESHOLD &&
	previousLastIndex.current !== lastActionIndex &&
	reportActionSize.current > sortedVisibleReportActions.length &&
	hasNewestReportAction
	) {
	setIsFloatingMessageCounterVisible(false);
	reportScrollManager.scrollToBottom();
	}

[Due for payment 2025-09-19] [$250] mWeb - Chat - Chat doesn't auto-scroll when a payment is received with chat opened #65792

Description

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Activity

melvin-bot commented on Jul 9, 2025

dmkt9 commented on Jul 10, 2025

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

melvin-bot commented on Jul 11, 2025

melvin-bot commented on Jul 11, 2025

melvin-bot commented on Jul 15, 2025

c3024 commented on Jul 15, 2025

98 remaining items

melvin-bot commented on Sep 22, 2025

garrettmknight commented on Sep 22, 2025

dmkt9 commented on Sep 23, 2025

garrettmknight commented on Sep 23, 2025

garrettmknight commented on Sep 23, 2025

DylanDylann commented on Sep 25, 2025

BugZero Checklist:

Regression Test Proposal

Precondition: Log in with two different accounts (User A,User B)

Test:

garrettmknight commented on Sep 29, 2025

Payment Summary

garrettmknight commented on Nov 11, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions