Skip to content

[Due for payment 2025-08-01] [$250] Expense - Chat does not scroll down after creating expense #65124

Closed

Description

@mitarachim

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.72-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?/tests/view/6375437
Email or phone of affected tester (no customers): sdhiuhsisudhsdisi@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Open 1:1 DM.
  3. Send enough messages so the report is scrollable.
  4. Open another chat.
  5. Go back to the previous chat with many messages.
  6. Click + > Create expense > Manual.
  7. Submit an expense to the user.

Expected Result:

Report will scroll down to reveal the expense preview after submitting an expense to the user.

Actual Result:

Report does not scroll down to reveal the expense preview after submitting an expense to the user.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6872080_1751097520510.20250628_155711.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021939753473434995187
  • Upwork Job ID: 1939753473434995187
  • Last Price Increase: 2025-07-14
  • Automatic offers:
    • thelullabyy | Contributor | 108101059
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @joekaufmanexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jun 28, 2025
  2. melvin-bot commented on Jun 28, 2025

    @melvin-bot

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

  3. github-actions commented on Jun 28, 2025

    @github-actions
    Contributor

    👋 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.
  4. melvin-bot commented on Jun 28, 2025

    @melvin-bot

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

  5. melvin-bot commented on Jun 28, 2025

    @melvin-bot

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

  6. BlameGPT commented on Jun 28, 2025

    @BlameGPT
    Contributor

    Possible culprit PRs for this issue

    Exploratory PRs

  7. 61 remaining items

  8. melvin-bot commented on Jul 25, 2025

    @melvin-bot

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

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

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

  9. melvin-bot commented on Jul 25, 2025

    @melvin-bot

    @akinwale @joekaufmanexpensify 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]

  10. joekaufmanexpensify commented on Jul 28, 2025

    @joekaufmanexpensify
    Contributor

    @akinwale could you handle checklist here so we can prep for payment later this week?

  11. akinwale commented on Jul 29, 2025

    @akinwale
    Contributor

    BugZero Checklist:

    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:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [@akinwale] 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: N/A

    • [@akinwale] 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: N/A

    • [@akinwale] 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

    Test:

    1. Launch Expensify.
    2. Open a 1:1 DM.
    3. Send a number of messages, enough to make the report scrollable.
    4. Open a different chat or report.
    5. Navigate back to the previous 1:1 DM chat.
    6. Click + > Create expense > Manual.
    7. Submit the expense to the user.
    8. Verify that the report scrolls to the end of the chat after the expense preview has been displayed.

    Do we agree 👍 or 👎?

  12. joekaufmanexpensify commented on Jul 31, 2025

    @joekaufmanexpensify
    Contributor

    Regression test issue is here.

  13. joekaufmanexpensify commented on Jul 31, 2025

    @joekaufmanexpensify
    Contributor

    All set to pay tomorrow!

  14. joekaufmanexpensify commented on Jul 31, 2025

    @joekaufmanexpensify
    Contributor

    Payment summary:

  15. joekaufmanexpensify commented on Aug 1, 2025

    @joekaufmanexpensify
    Contributor

    @thelullabyy $250 sent and contract ended!

  16. joekaufmanexpensify commented on Aug 1, 2025

    @joekaufmanexpensify
    Contributor

    Upwork job closed

  17. joekaufmanexpensify commented on Aug 1, 2025

    @joekaufmanexpensify
    Contributor

    @akinwale please request payment at your earliest convenience. Closing as this is otherwise all set 👍

  18. isabelastisser commented on Aug 5, 2025

    @isabelastisser
    Contributor

    @akinwale has submitted payment for this report on ND here.

    SO: https://stackoverflowteams.com/c/expensify/questions/7582

    Vendor found in VML: True. Status: Active

    Amount requested: $250. Matches the payment summary here.

    I am not already the BZ assignee. I have approved this payment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions