Report - Report view shows skeleton during each visit

[IuliiaHerets]

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.21-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
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): [email protected]
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 any report.
3. Go to another report.
4. Switch back and forth between reports.

Expected Result:

If the report is opened previously, it should not show skeleton after the subsequent visits.

Actual Result:

When the report is opened previously, it stll shows skeleton after the subsequent visits.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6787846_1743418864626.Screen_Recording_2025-03-31_at_18.51.55.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @martasudol

[melvin-bot]

Triggered auto assignment to @maddylewis (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]

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

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

[mountiny]

@martasudol @adhorodyski

[mountiny]

Not a blocker, we reverted the changes before on purpose becuase we were seeing other unwanted issues. We are waiting for Auth PR to be deployed later today that should hopefully help us bring this App change back

[melvin-bot]

@martasudol Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[mountiny]

@adhorodyski is working on updated solution today

[melvin-bot]

@martasudol 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[adhorodyski]

Marta is assigned, but this is not overdue. This is covered in the recent PRs under #58388

[melvin-bot]

@martasudol 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

[martasudol]

Should we close it?

[mountiny]

Yes, thanks