Skip to content

Migrate InteractionManager - (Newly added usages) batch 1#94171

Merged
roryabraham merged 17 commits into
Expensify:mainfrom
software-mansion-labs:mrejdak/migrate-interactionmanager-leftovers-1
Jul 1, 2026
Merged

Migrate InteractionManager - (Newly added usages) batch 1#94171
roryabraham merged 17 commits into
Expensify:mainfrom
software-mansion-labs:mrejdak/migrate-interactionmanager-leftovers-1

Conversation

@mrejdak

@mrejdak mrejdak commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Migration of remaining usages of InteractionManager.

This PR also migrates the ConfirmModal fromsrc/components/ContactPermissionModal/index.native.tsx to useConfirmModal and refactors the component into a hook src/hooks/ContactPermissionModal/index.native.ts.

Fixed Issues

$ #71913
$ #83071
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

ContactPermissionModal

Prerequisites: Have an account with a workspace created and use a simulator/device that hasn't been prompted for contact permissions yet

  1. Navigate to Account -> Troubleshoot and press Clear cache and restart
  2. Go back and press FAB -> Create expense
  3. Input any value and press Next
  4. Attempt to change the destination
  5. A contact import modal will appear
  6. Select "No thanks" / Select "Continue" / Click outside to close it
  7. Verify that the input box focuses correctly

SearchRouter.tsx

  1. Create a new account with a very long name
  2. Create a workspace
  3. Open search router (Cmd + K on web) and type "in:"
  4. Select the suggested long name (so that the input exceeds the right end of the input box)
  5. Verify that the input focus is correct

useSearchBulkActions.tsx

  1. Navigate to Spend -> Reports
  2. Create a report with an expense
  3. Long press on the report and press Select
  4. From the dropdown menu on top select Delete -> Confirm
  5. Verify that the report is deleted correctly

useSelectionModeReportActions.tsx

  1. Create a new report with two expenses
  2. Submit the report
  3. Long press one of the reports and press Select
  4. From the dropdown menu on top select Hold and confirm it (input any reason)
  5. Now select both reports and from the dropdown menu on top select Approve
  6. Verify that the hold menu opens correctly

Offline tests

N/A

QA Steps

Same as Tests.

  • 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

useSearchBulkActions.tsx

leftovers-3-delete-report.mov
iOS: Native

ContactPermissionModal

leftovers-1-contacts.mov

useSelectionModeReportActions.tsx

leftovers-4-onhold.mov
iOS: mWeb Safari
MacOS: Chrome / Safari

SearchRouter.tsx

leftovers-2-search-input.mov

@codecov

codecov Bot commented Jun 22, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
...nents/Reactions/ReportActionItemEmojiReactions.tsx 46.66% <ø> (ø)
src/hooks/useSelectionModeReportActions.ts 94.28% <ø> (+2.61%) ⬆️
src/hooks/useContactPermissionModal/index.ts 0.00% <0.00%> (ø)
...rc/components/Search/SearchRouter/SearchRouter.tsx 57.33% <60.00%> (+0.28%) ⬆️
src/hooks/useSearchBulkActions.ts 53.67% <66.66%> (+0.06%) ⬆️
src/hooks/useExpenseActions.ts 0.00% <0.00%> (ø)
src/pages/iou/request/ParticipantSearchResults.tsx 0.66% <0.00%> (+<0.01%) ⬆️
...rc/hooks/useContactPermissionModal/index.native.ts 0.00% <0.00%> (ø)
... and 153 files with indirect coverage changes

@mrejdak
mrejdak marked this pull request as ready for review June 25, 2026 09:52
@mrejdak
mrejdak requested review from a team as code owners June 25, 2026 09:52
@melvin-bot
melvin-bot Bot requested review from Pujan92, heyjennahay and ikevin127 and removed request for a team June 25, 2026 09:52
@melvin-bot

melvin-bot Bot commented Jun 25, 2026

Copy link
Copy Markdown

@Pujan92 @ikevin127 One of you needs to 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]

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 40a4ba93e0

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/hooks/useContactPermissionModal/index.native.ts
Comment thread src/hooks/useContactPermissionModal/index.native.ts Outdated
Comment thread src/hooks/useContactPermissionModal/index.native.ts Outdated
Comment thread src/hooks/useContactPermissionModal/index.native.ts Outdated
@mrejdak

mrejdak commented Jun 25, 2026

Copy link
Copy Markdown
Contributor Author

I'll be OOO starting tomorrow, so @collectioneur will take care of this PR from now on

@Pujan92

Pujan92 commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (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 verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
Simulator.Screen.Recording.-.iPhone.15.Pro.-.2026-06-25.at.21.06.16.mov
Simulator.Screen.Recording.-.iPhone.15.Pro.-.2026-06-26.at.00.07.55.mov
Simulator.Screen.Recording.-.iPhone.15.Pro.-.2026-06-30.at.13.46.20.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-06-26.at.00.02.25.mov
Screen.Recording.2026-06-25.at.23.59.36.mov

Comment thread src/hooks/useSearchBulkActions.ts Outdated
const validTransactions = Object.fromEntries(Object.entries(allTransactions ?? {}).filter((entry): entry is [string, Transaction] => entry[1] !== undefined));
InteractionManager.runAfterInteractions(() => {
TransitionTracker.runAfterTransitions({
waitForUpcomingTransition: true,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need this bcoz I see the delay in opening the delete modal?

Simulator.Screen.Recording.-.iPhone.15.Pro.-.2026-06-26.at.00.12.55.mov

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I've confirmed it isn't needed here because the delete modal already waits for the options modal to close. Thanks!

Screen.Recording.2026-06-29.at.11.02.46.mov

@Pujan92

Pujan92 commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

@collectioneur plz fix the conflicts

@collectioneur

Copy link
Copy Markdown
Contributor

@Pujan92 resolved 🫡

@Pujan92 Pujan92 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!!

@melvin-bot
melvin-bot Bot requested a review from roryabraham June 30, 2026 09:13
Comment thread src/hooks/useContactPermissionModal/index.native.ts Outdated
Comment thread src/hooks/useContactPermissionModal/index.ts Outdated
@collectioneur

Copy link
Copy Markdown
Contributor

@roryabraham all fixed, thanks!

@roryabraham
roryabraham merged commit 9ce3910 into Expensify:main Jul 1, 2026
34 checks passed
@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

🚧 roryabraham has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

OSBotify commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

OSBotify commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.4.26-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Help site review: no changes required.

I reviewed the changes in this PR and no updates are needed to the help site files under docs/articles.

This PR is a purely internal engineering refactor with no user-facing behavior change:

  • Migrates remaining InteractionManager.runAfterInteractions usages to TransitionTracker.runAfterTransitions (ReportActionItemEmojiReactions, SearchRouter, useExpenseActions, useSearchBulkActions, useSelectionModeReportActions, ParticipantSearchResults).
  • Refactors ContactPermissionModal from a component into the useContactPermissionModal hook (using useConfirmModal).

None of these touch feature behavior, UI copy, tab/settings labels, pricing, or workflows that the help site documents — the contact-permission prompt, search router, and bulk/selection actions all keep their existing user-facing behavior. So there is nothing to document or update.

No draft docs PR was created since no changes are required.

@unzig21

unzig21 commented Jul 2, 2026

Copy link
Copy Markdown

Deploy Blocker #95114 was identified to be related to this PR.

huult pushed a commit to huult/App that referenced this pull request Jul 2, 2026
…miss

Restore the InteractionManager deferral around the Search bulk-delete
dispatch that Expensify#94171 removed. Dispatching the delete synchronously as the
confirm modal dismissed caused the deletion to be dropped on iOS, leaving the
selected expenses undeleted (Expensify#95114).

Co-authored-by: Marco Chávez <marcochavezf@users.noreply.github.com>
@OSBotify

OSBotify commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.4.27-2 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants