[$500] Chat–Approaching the beginning of the conversation, the " skeleton loader " does not appear

[lanitochka17]

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.3.91-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Issue found when executing PR #26166

Action Performed:

1. Open https://staging.new.expensify.com/.
2. Log in with any user
3. Navigate to 1:1 conversation
4. Scroll to the top of the chat list

Expected Result:

As you approach the top, you should see a "skeleton loader"

Actual Result:

Approaching the beginning of the conversation, the " skeleton loader " does not appear

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

Windows: Chrome

Bug6250719_1698259439669.Bidirectional_pagination.1.mp4

MacOS: Desktop

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~016977264e77e19b4a
• Upwork Job ID: 1717265961042673664
• Last Price Increase: 2023-11-01

[melvin-bot]

Triggered auto assignment to @sakluger (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

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

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

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

[rayane-djouah]

Not able to reproduce on main

[abeebridwan]

@sakluger @aimane-chnaif
I can't reprodue this locally on the main branch
even the bottom skeleton is not working locally

[aimane-chnaif]

@lanitochka17 can you please confirm that you're still able to reproduce on latest staging?

[abeebridwan]

@aimane-chnaif
the bottom skeleton is still working on the staging ... not the top

[sakluger]

@lanitochka17 can you confirm if this is still reproduceable? None of us can reproduce it.

[lanitochka17]

Issue not reproducible on latest build 1.3.93-1
Windows10/Chrome

Skeleton.mp4

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[aimane-chnaif]

QA team didn't reproduce it. @sakluger let's close