[Due for payment 2025-03-25] [$250] Create Expense - The app does not scroll to the bottom when a new expense is created.

[mitarachim]

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

---

Version Number: 9.1.13-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5741323
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Web, mweb
App Component: Chat Report View

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Go to any chat
3. scroll up until the latest comment is out of view.
4. Create an expense

Expected Result:

When a new expense is created, the app should automatically scroll to the bottom.

Actual Result:

The app does not scroll to the bottom when a new expense is created

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6770398_1741934366298.bandicam_2025-03-14_09-33-13-118.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021900480710794741851
• Upwork Job ID: 1900480710794741851
• Last Price Increase: 2025-03-14
• Automatic offers:
• huult | Contributor | 106523351

Issue Owner

Current Issue Owner: @greg-schroeder

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[linhvovan29546]

Offending PR #57901 should we revert it rather than fix it? @madmax330 @c3024

[linhvovan29546]

Proposal

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

Create Expense - The app does not scroll to the bottom when a new expense is created

What is the root cause of that problem?

Offending PR #57901

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

I think we should revert the offending PR

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

N/A

What alternative solutions did you explore? (Optional)

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.

[huult]

I am checking

[rojiphil]

@huult Please check if we need to still call reportScrollManager.scrollToBottom(); here to scroll down along with setIsScrollToBottomEnabled. We had removed it at a later stage

[huult]

@rojiphil I guess the case of this issue is different from ours, and they did not call onLayout. So, I think we should call reportScrollManager.scrollToBottom(); and add it back.

[rojiphil]

I guess the case of this issue is different from ours, and they did not call onLayout. So, I think we should call reportScrollManager.scrollToBottom(); and add it back.

I agree. Can you please raise a quick PR for this as this is a small change?

[huult]

yes

[rojiphil]

Please tag me once the PR is ready and I will review the same as this is caused by our PR.

[huult]

yes I will open the pr within an hour

[huult]

@rojiphil The PR is ready

[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.1.13-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] call scrollToBottom when create new expense #58469

If no regressions arise, payment will be issued on 2025-03-24. 🎊

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

• @rojiphil requires payment through NewDot Manual Requests
• @huult requires payment automatic offer (Contributor)
• @c3024 requires payment through NewDot Manual Requests

[melvin-bot]

@rojiphil / @c3024 @greg-schroeder @rojiphil / @c3024 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

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

• [CP Staging] call scrollToBottom when create new expense #58469

If no regressions arise, payment will be issued on 2025-03-25. 🎊

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

• @rojiphil requires payment through NewDot Manual Requests
• @huult requires payment automatic offer (Contributor)
• @c3024 requires payment through NewDot Manual Requests

[melvin-bot]

@rojiphil / @c3024 @greg-schroeder @rojiphil / @c3024 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[greg-schroeder]

Processing today

[rojiphil]

@greg-schroeder Let us close this out as this was fixed as part of the regression fix. No payment is due to anyone here.