[Due for payment 2025-04-10] [Better Expense Report View] iOS - Reports - Report view is blank and does not show skeleton when fetching data

[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: 9.1.16-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+kok1@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• Log in with Expensifail account
• Account has some expenses
• Perform a fresh log in so that those expense reports are not opened yet

1. Launch ND or hybrid app
2. Go to Reports
3. Tap bookmark icon
4. Tap Expense Reports
5. Open any expense report

Expected Result:

Report will show skeleton when fetching data

Actual Result:

Report is blank while fetching data

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6777042_1742486137686.ScreenRecording_03-20-2025_23-52-47_1.1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @Kicu

[melvin-bot]

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

This view is behind a beta. NAB. cc @Kicu