feat: Migrate lists to interactive keyboard dismissal

[chrispader]

@roryabraham @trjExpensify @parasharrajat

Explanation of Change

Uses the new newly added components and logic from #71438 and migrates current list pages to integrate interactive keyboard dismissal.

This PR adapts the lists on:

• ReportScreen
• MoneyRequestReportActionView

Fixed Issues

$ #54270
PROPOSAL:

Tests

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

• 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
  • MacOS: Desktop
• 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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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 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

Screen_Recording_20260130_114326_New.Expensify.mp4

iOS: Native

Simulator.Screen.Recording.-.iPhone.17.Pro.-.2026-01-29.at.17.09.45.mov

[melvin-bot]

@parasharrajat Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[chrispader]

@mountiny @roryabraham merged conflicts on this one after the previous PR has been merged. Will test interactive keyboard dismissal later

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/CONST/index.ts	87.39% <ø> (+3.36%)	⬆️
...s/ScreenWrapper/ScreenWrapperOfflineIndicators.tsx	100.00% <100.00%> (ø)
...fflineIndicatorKeyboardHandlingStyles/index.ios.ts	100.00% <100.00%> (ø)
src/hooks/useReportScrollManager/index.native.ts	75.00% <100.00%> (+5.00%)	⬆️
src/pages/Search/SearchMoneyRequestReportPage.tsx	0.00% <ø> (ø)
...omposerWithSuggestions/ComposerWithSuggestions.tsx	58.89% <ø> (ø)
...report/ReportActionCompose/ReportActionCompose.tsx	68.99% <100.00%> (ø)
src/pages/inbox/report/ReportActionsView.tsx	76.92% <ø> (ø)
...bleKeyboardAvoidingViewInReportScreen/index.ios.ts	100.00% <100.00%> (ø)
...es/inbox/report/useReportFooterStyles/index.ios.ts	100.00% <100.00%> (ø)
... and 21 more
... and 126 files with indirect coverage changes

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4762b4ce65

ℹ️ 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]

Don’t mutate JS refs inside a Reanimated worklet

useAnimatedReaction runs on the UI thread; writing to scrollingVerticalOffsetRef.current inside the worklet won’t update the JS thread value. The ref is later read on the JS side in ReportActionsList to decide unread-marker placement and when to mark messages read, so it can stay at the initial value and treat the user as always at the bottom (e.g., unread messages marked read while scrolled up). Use a SharedValue end‑to‑end or runOnJS to update the JS ref.

Useful? React with 👍 / 👎.

[mountiny]

thanks

[chrispader]

Today's update:

• Started testing interactive keyboard dismissal on both Android and iOS
  • Basic keyboard dismissal works great on both Android and iOS
• On iOS, there are some visible glitches that i'm investigating.
  • Fixed minor issues with our logic using useKeyboardHandler already.
• Testing whether latest react-native-keyboard-controller library fix some of the issues

[chrispader]

Update: Bumping react-native-keyboard-controller to latest version as in this PR fixes most issues.

[chrispader]

Both iOS and Android work reliably well now, i've added screen recordings above. The only thing blocking us right now is this RKNC issue. Right now i have a workaround on iOS, which can cause a slight flicker since we have to omit the first keyboard drag event.

Trying to work out the issue with @kirillzyusko and i'm addressing failing checks right now

[chrispader]

@kirillzyusko already found a fix for the RNKC issue mentioned above. The fix won't be published until new minor version 1.21.0 which won't be released very soon, therefore i added a patch file.

We'll need to hold this PR on this RKNC version bump PR though.

[github-actions]

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️