[Performance] Short-circuit reportAttributes recompute on timeSkew writes

[adhorodyski]

Explanation of Change

Sibling of merged PR #88592 which dropped ONYXKEYS.NETWORK entirely from the visibleReportActions derivation because that compute never read isOffline. The target here — the reportAttributes derivation at src/libs/actions/OnyxDerived/configs/reportAttributes.ts — does read isOffline via getIsOffline() from the in-memory @libs/NetworkState module. The comment at line 99 (pre-change) admitted the NETWORK Onyx dep was kept purely to trigger recompute when offline state flipped.

ONYXKEYS.NETWORK receives a timeSkew write on every API response via src/libs/HttpUtils.ts:86 (addSkewList matches OpenReport, ReconnectApp, OpenApp). Each such write fired a full reportAttributes recompute across all reports, which feeds LHN brick-road rendering — but the output only changes when isOffline binary-edge-transitions, not on every timeSkew update.

Fix: short-circuit the compute when NETWORK is the sole trigger AND isOffline is unchanged since the last run. NETWORK stays in dependencies[] so genuine offline flips still invalidate and recompute.

Mechanism:

• New module-level tracker previousIsOffline: boolean | undefined.
• Inside compute: if sourceValues contains only ONYXKEYS.NETWORK as trigger and getIsOffline() === previousIsOffline, return currentValue unchanged.
• Otherwise update previousIsOffline and run the normal compute path.

Why keep the NETWORK dep instead of dropping it like #88592? The downstream call chain SidebarUtils.getReasonAndReportActionThatHasRedBrickRoad → getReceiptUploadErrorReason → getOneTransactionThreadReportAction branches on isOffline && pendingAction === DELETE (see src/libs/ReportActionsUtils.ts around line 1969). Output genuinely changes on offline flip. Dropping the dep would leave brick-road status stale until the next business-event recompute.

Fixed Issues

$
PROPOSAL:

Tests

1. Open the app on a narrow layout with a warm LHN (several visited reports in cache).
2. Open React DevTools Profiler on the web dev server.
3. Start recording, tap a recently-visited report in LHN, stop after the report renders.
4. Filter the timeline / spans by reportAttributes compute invocations.
5. Verify: on the main branch this sibling PR would show the same high count as visibleReportActions did before [Performance] Drop dead NETWORK dependency from visibleReportActions derivation #88592; with this PR the reportAttributes compute count during warm nav drops to the number of genuine business-state triggers (usually 0–1, not N-per-API-response).
6. Repeat on a wide layout.

• Verify that no errors appear in the JS console.

Offline tests

1. On a report that has a DELETE-IOU pending action, confirm brick-road state while online.
2. Toggle offline (DevTools → Network → Offline, or airplane mode on device).
3. Verify brick-road updates per offline DELETE-IOU visibility rule (deleted IOU becomes visible).
4. Toggle back online; verify the indicator reverts.
5. This validates that the short-circuit does NOT suppress recompute on actual isOffline transitions (i.e. the NETWORK dep is still honored for semantic changes).

QA Steps

Same as Tests and Offline tests above.

• 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • 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)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• 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)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• 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.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• 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

No UI change — see span-count delta described in Tests.

Android: mWeb Chrome

No UI change — see span-count delta described in Tests.

iOS: Native

No UI change — see span-count delta described in Tests.

iOS: mWeb Safari

No UI change — see span-count delta described in Tests.

MacOS: Chrome / Safari

No UI change — see span-count delta described in Tests.

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
...bs/actions/OnyxDerived/configs/reportAttributes.ts	96.96% <87.50%> (-0.50%)	⬇️
... and 21 files with indirect coverage changes