LHN - LHN displayed blank for a 1-2 second when user rapidly scrolled up

[kbecciv]

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: 1.4.61-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

Precondition: user should be signed in

1. Open app
2. Scroll down to the very bottom
3. Rapidly scroll up to the very top

Expected Result:

LHN should be properly displayed during scrolling

Actual Result:

LHN displayed blank for a 1-2 second when user rapidly scrolled up

Workaround:

n/a

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6442317_1712583361025.RPReplay_Final1712583323.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

[mountiny]

I dont think this is a blocker, this has been happening for a while, it just might be more visible on some devices than others

[mountiny]

Its just a nature of the FlashList, only some of the rows are rendered for performance reasons so when user scrolls so fast the top rows will not be rendered yet.

[mountiny]

I believe we can close this

[roryabraham]

yeah, this is just a performance issue. Let's close this for now, but in the next performance audit maybe we can try to introduce a "scroll drop" metric