Auto-scroll to next report preview that requires action

[MelvinBot]

Explanation of Change

When a report chat shows the "action badge" Floating Message Counter, the badge points at the oldest report preview that still requires action (approve/pay/etc.). Previously, after the user resolved that preview, nothing moved the list to the next preview that needs attention — the user had to manually scroll to find it.

This change makes the list automatically follow the badge target. The badge target is derived from reportAttributes.actionTargetReportActionID, which advances to the next-actionable report preview once the current one is resolved. By watching that value, we scroll to the new target via the existing scrollToActionBadgeTarget machinery (reportScrollManager.scrollToIndex).

Key safeguards:

• Directional guard: the list is inverted (index 0 = newest at the bottom, higher index = older at the top). The badge always targets the oldest actionable preview, so resolving it advances the target to a newer preview, i.e. a lower index. We only auto-scroll when the new target index is strictly lower than the previous target's index. This ensures we only scroll downward to the next actionable preview and never jump upward/backward (e.g. when older actions are loaded in via pagination).
• Same gating as the existing action-badge feature: the auto-scroll is gated behind !isProduction, matching the rollout gating already applied to the action badge / onActionBadgePress behavior in this file, so it does not change production behavior.

The change is contained to src/pages/inbox/report/ReportActionsList.tsx and reuses existing state and helpers (actionTargetReportActionID, actionBadgeTargetIndex, renderedVisibleReportActions, scrollToActionBadgeTarget) rather than threading new callbacks down through the approve/pay action buttons.

Fixed Issues

$ #90278
PROPOSAL:

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

Suggested manual verification (dev environment, where isProduction is false):

1. Open a workspace chat / report that has two or more older report previews requiring action (e.g. multiple reports awaiting Approve or Pay) such that the action badge / Floating Message Counter appears.
2. Tap the action badge — verify the list scrolls up to the oldest report preview that requires action.
3. Click Approve (or Pay) on that oldest report preview.
4. Verify the list automatically smooth-scrolls down to the next report preview that still requires action.
5. Repeat until no actionable previews remain; verify no further auto-scroll occurs once the badge is gone.
6. Verify there is no unexpected upward/backward scroll while paginating older messages.
7. Verify that no errors appear in the JS console.

• Verify that no errors appear in the JS console

Offline tests

Same as Tests. The auto-scroll reacts to the locally-derived reportAttributes state, so it behaves the same offline once the optimistic approve/pay update is applied.

QA Steps

// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.

• 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
  • 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[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 Δ
src/pages/inbox/report/ReportActionsList.tsx	77.03% <50.00%> (-0.78%)	⬇️
... and 7 files with indirect coverage changes