Prevent infinite spinner when no transactions to load

[deetergp]

Explanation of Change

shouldWaitForTransactions kept a money-request/invoice report in the loading state whenever its cached total was non-zero and no transactions were present. If a report's transactions can never load (e.g. the owning report was orphaned by an account merge), this showed the loading skeleton forever. Now, once the initial report actions have loaded at least once (hasOnceLoadedReportActions) and still no transactions arrived, we stop treating a stale total as "still loading", so the report resolves to its empty/not-found state instead of spinning. The pre-load window (waiting while actions are still loading) is unchanged, so there is no empty-state flash on normal reports.

This is a defense-in-depth companion to the backend fix in Auth#22541.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/645644
PROPOSAL:

Tests

1. Open a normal expense/IOU report that has transactions and verify the transactions list loads (no infinite skeleton, no empty-state flash).
2. Open the affected expense from the linked issue (an expense whose owning report was orphaned by an account merge) in New Expensify.
3. Verify it no longer shows a permanent loading skeleton — once report actions finish loading it resolves to the empty/not-found state.
4. Automated: tests/unit/libs/MoneyRequestReportUtils.ts covers shouldWaitForTransactions (waits while loading / before first load, stops once loaded with no transactions, never waits offline). Run npx jest tests/unit/libs/MoneyRequestReportUtils.ts — 13/13 pass.

• Verify that no errors appear in the JS console

Offline tests

1. Go offline.
2. Open a money request report.
3. Verify it renders immediately and does not show an indefinite loading skeleton (offline short-circuits the wait).

QA Steps

Same as Tests, using the affected account/expense from the linked issue. A clean reproduction requires an expense whose owning report was orphaned by an account merge; on a normal report, confirm there is no regression (transactions load, no empty-state flash).

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[deetergp]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6c0e1a978e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep waiting while transactions can still populate

When hasOnceLoadedReportActions flips true before the derived transactions collection has caught up, this now stops waiting even though report.total still says the money request has expenses. useReportTransactionsCollection returns an empty object until REPORT_TRANSACTIONS_AND_VIOLATIONS is recomputed, and MoneyRequestReportActionsList treats empty actions plus empty transactions as the empty-state view once isLoadingInitialReportActions is false, so a normal non-empty report can briefly or incorrectly render as empty instead of continuing to show the skeleton until its transactions arrive.

Useful? React with 👍 / 👎.