[Due for payment 2026-03-30][$250] Report - Skeleton loading when Admin refreshes the page and opens members's report

[jponikarchuk]

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.3.11-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13176933/test-cases/41237705
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: MacBook Air 15.7.3 Chrome
App Component: Money Requests

Action Performed:

1. Admin, invite a Member to the workspace
2. Member, create an expense in the Admin's workspace chat
3. Admin, open the Member's report, close it and navigate away from the chat
4. Admin, Refresh the browser
5. Admin, navigate to Member's workspace chat and open the report

Expected Result:

The report loads successfully

Actual Result:

After admin refreshes the browser and navigates to the member's workspace chat, the report preview shows empty state. When opening it, it shows skeleton loading

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022017063370358951446
• Upwork Job ID: 2017063370358951446
• Last Price Increase: 2026-01-30

Issue Owner

Current Issue Owner: @

[melvin-bot]

Triggered auto assignment to @greg-schroeder (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 @luacmartins (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.

[luacmartins]

@MelvinBot find the cause

[OSBotify]

Investigation Summary

Classification: Unable to determine with high confidence - NEEDS INVESTIGATION

Current Labels: DeployBlockerCash (App deploy blocker)

Recommendation: NEEDS INVESTIGATION

I was unable to identify a specific causing PR with high confidence after reviewing the PRs in the current staging deploy (9.3.11-1). The bug involves report previews showing skeleton loading after a browser refresh, which is only reproducible on staging.

Evidence

The issue describes:

• Admin refreshes browser after viewing a member's expense report
• Report preview shows empty state
• Opening the report displays skeleton loading indefinitely
• Only reproducible on staging (not production)
• Affects workspace chat reports with expense previews

Analysis

I reviewed the following types of PRs in the deploy checklist:

• Report data loading and caching changes
• Onyx selector modifications
• useOnyx refactors and canBeMissing parameter changes
• Report action and preview rendering updates
• Derived value additions

The most common causes for this type of issue are:

1. Changes to Onyx selectors that affect report data availability after refresh
2. Modifications to canBeMissing parameters in useOnyx calls
3. Changes to report metadata or loading state logic
4. Derived value issues that affect report data dependency chains

However, I could not pinpoint a specific PR that clearly modifies the report preview or report loading logic in a way that would cause this specific symptom.

Next Steps

1. Reproduce the issue on staging following the exact steps in the issue description
2. Check browser console for errors or warnings during reproduction
3. Inspect Onyx state before and after refresh to see what data is missing
4. Tag the issue author @Expensify/Applause for additional reproduction details
5. Check for related deploy blockers - there may be multiple issues stemming from the same root cause

@luacmartins - As the assigned deploy blocker owner, could you help coordinate reproduction and gather additional debug information? The skeleton loading suggests the app is waiting for data that never arrives after a refresh, which points to a data loading or caching issue introduced in this staging deploy.

Labels: Keeping DeployBlockerCash until root cause is identified