Skip to content

[Due for payment 2025-03-21] [$250] Chat - Unable to scroll to the top when scrolling up at moderate speed #58160

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.11-1
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: Exp
Email or phone of affected tester (no customers): applausetester+h9ne229@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Chat Report View

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to chat.
  3. Send a few attachments (at least three on web & desktop, at least four on Android & iOS) to the chat so that the chat is scrollable.
  4. Scroll up at a moderate speed (not too fast and not too slow).

Expected Result:

Chat will be scrolled to the top smoothly.

Actual Result:

The chat is stuck in the middle when scrolling up at a moderate speed.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6766902_1741662544157.iOS.mp4
Bug6766902_1741662366740.20250311_110516.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021899378621478971427
  • Upwork Job ID: 1899378621478971427
  • Last Price Increase: 2025-03-11
  • Automatic offers:
    • ZhenjaHorbach | Contributor | 106487455
Issue OwnerCurrent Issue Owner: @jliexpensify

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Mar 11, 2025

    @melvin-bot

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

  4. melvin-bot commented on Mar 11, 2025

    @melvin-bot

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

  5. github-actions commented on Mar 11, 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.
  6. jliexpensify commented on Mar 11, 2025

    @jliexpensify
    Contributor

    @MariaHCD I think this is definitely an issue - I can't reproduce the issue exactly as Applause have written the steps, but I noticed that when I scroll up, I can never reach the top. It's just a constant scroll up, like in this video:

    2025-03-11_15-21-56.mp4
  7. MariaHCD commented on Mar 11, 2025

    @MariaHCD
    Contributor

    Interestingly, I was able to reproduce the issue once on staging web but then I refreshed and I can't seem to reproduce it anymore:

    Screen.Recording.2025-03-11.at.11.06.47.AM.mov

    I wasn't able to reproduce on staging desktop at all 🤔

    Screen.Recording.2025-03-11.at.11.08.17.AM.mov
  8. 41 remaining items

  9. melvin-bot commented on Mar 14, 2025

    @melvin-bot

    @ZhenjaHorbach @jliexpensify @ZhenjaHorbach 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. martasudol commented on Mar 18, 2025

    @martasudol
    Contributor

    Hey, the fix has already been merged. Is there anything else needed from my side, or can we close this issue?

  11. ZhenjaHorbach commented on Mar 18, 2025

    @ZhenjaHorbach
    Contributor

    Hey, the fix has already been merged. Is there anything else needed from my side, or can we close this issue?

    Remaining payment and regression period until 21.03 !

  12. jliexpensify commented on Mar 18, 2025

    @jliexpensify
    Contributor

    @ZhenjaHorbach any checklist needed?

  13. jliexpensify commented on Mar 18, 2025

    @jliexpensify
    Contributor

    Payment Summary

    https://www.upwork.com/jobs/~021899378621478971427

  14. ZhenjaHorbach commented on Mar 18, 2025

    @ZhenjaHorbach
    Contributor

    @ZhenjaHorbach any checklist needed?

    I think it will be useful
    I will fill out the checklist tomorrow !

  15. melvin-bot commented on Mar 19, 2025

    @melvin-bot
  16. jliexpensify commented on Mar 19, 2025

    @jliexpensify
    Contributor

    Hmm @ZhenjaHorbach - is there a regression here?

  17. jasperhuangg commented on Mar 19, 2025

    @jasperhuangg
    Contributor

    Sorry, there's no regression here. I mistakenly marked this PR as causing a deploy blocker.

  18. jliexpensify commented on Mar 19, 2025

    @jliexpensify
    Contributor

    Np, ty Jasper!

  19. ZhenjaHorbach commented on Mar 19, 2025

    @ZhenjaHorbach
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    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:
    • [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.

      The fix was made by the developer of the PR which caused regression

    • [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: NA

    • [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.

    Regression Test Proposal

    Test:

    1. Open App
    2. Go to chat
    3. Send a few attachments (at least three on web & desktop, at least four on Android & iOS) to the chat so that the chat is scrollable.
    4. Scroll up at a moderate speed (not too fast and not too slow)
    5. Verify that chat is scrolled to the top smoothly.

    Do we agree 👍 or 👎

  20. jliexpensify commented on Mar 21, 2025

    @jliexpensify
    Contributor

    Paid, and job closed!

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions