Skip to content

Mobile search-router is a RHP on native - #77380

Merged
mountiny merged 15 commits into
Expensify:mainfrom
software-mansion-labs:feat/migrate-search-router-to-navigation
Jan 12, 2026
Merged

mountiny merged 15 commits into
Expensify:mainfrom
software-mansion-labs:feat/migrate-search-router-to-navigation

Conversation

@jmusial

@jmusial jmusial commented Dec 11, 2025

Copy link
Copy Markdown
Contributor

Explanation of Change

This PR rewrites SearchRouterModal to use navigation RHP instead of modal for android and ios native.

Fixed Issues

$ #53493

PROPOSAL:

Tests

Perform tests for each of the pages

  1. Inbox page (/home)
  2. One of the Settings pages (ex. /settings/profile)
  3. Workspaces page (/workspaces)
  4. Report (/r/:reportID)
  5. Search report page (/search/r/:reportID)

Tests:

Basic navigation 1

  1. Click SearchButton -> Search router modal opens
  2. Close it using back button (if applicable) -> Should navigate to initial screen (or close keyboard first)

Basic navigation 2

  1. Click SearchButton -> Search router modal opens
  2. Close it using back search modal header back arrow -> Should navigate to initial screen

Advanced navigation 1

  1. Click SearchButton -> Search router modal opens
  2. Click one of the recent searches -> Should navigate to Search with recent search
  3. Press back -> navigates back to search router modal (change from current behaviour - it goes straight to 5 on web)
  4. Press back again -> navigates back to initial page

Advanced navigation 2

  1. Click SearchButton -> Search router modal opens
  2. Type in search phrase and press proposed result
  3. Press back -> navigates back to search router modal (change from current behaviour - it goes straight to 5 on web)
  4. Press back again -> navigates back to initial page

Offline tests

QA Steps

Same as tests

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 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 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
0080.android.native.mov
Android: mWeb Chrome

See: MacOS: Chrome / Safari

iOS: Native
0080.ios.native.mov
iOS: mWeb Safari

See: MacOS: Chrome / Safari

MacOS: Chrome / Safari

This PR does not change web implementation. Attaching small screen from chrome desktop as a sanity check & reference point.

On large screens the modal remains a POPOVER.

0080.chrome.desktop.mov

@codecov

codecov Bot commented Dec 11, 2025

Copy link
Copy Markdown

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/ROUTES.ts 12.60% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
...onents/Search/SearchRouter/SearchRouterContext.tsx 53.57% <ø> (ø)
...ch/SearchRouter/SearchRouterModal/index.native.tsx 100.00% <100.00%> (ø)
...ts/Search/SearchRouter/SearchRouterModal/index.tsx 0.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 75.00% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 8.33% <50.00%> (+0.12%) ⬆️
...on/AppNavigator/Navigators/RightModalNavigator.tsx 4.87% <0.00%> (-0.07%) ⬇️
...rch/SearchRouter/SearchRouterPage/index.native.tsx 0.00% <0.00%> (ø)
...nts/Search/SearchRouter/SearchRouterPage/index.tsx 0.00% <0.00%> (ø)
... and 2 more
... and 21 files with indirect coverage changes

@jmusial jmusial changed the title POC: Mobile search-router is a RHP POC: Mobile search-router is a RHP on native Dec 12, 2025
Comment on lines +1 to +3
/**
* On native devices SearchRouter is served from SearchRouterPage, on web from SearchRouterModal.
*/ function SearchRouterModal() {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
/**
* On native devices SearchRouter is served from SearchRouterPage, on web from SearchRouterModal.
*/ function SearchRouterModal() {
/**
* On native devices SearchRouter is served from SearchRouterPage, on web from SearchRouterModal.
*/
function SearchRouterModal() {

@jmusial jmusial changed the title POC: Mobile search-router is a RHP on native Mobile search-router is a RHP on native Dec 15, 2025
@jmusial
jmusial marked this pull request as ready for review December 15, 2025 12:22
@jmusial
jmusial requested review from a team as code owners December 15, 2025 12:22
@melvin-bot
melvin-bot Bot requested review from JmillsExpensify and parasharrajat and removed request for a team December 15, 2025 12:22
@melvin-bot

melvin-bot Bot commented Dec 15, 2025

Copy link
Copy Markdown

@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]

@melvin-bot
melvin-bot Bot removed the request for review from a team December 15, 2025 12:22
@mountiny

Copy link
Copy Markdown
Contributor

@parasharrajat can you test here

@JmillsExpensify JmillsExpensify 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.

All looks good, though product review isn't required for this one

@mountiny

Copy link
Copy Markdown
Contributor

@parasharrajat can you please make sure to review this one or ask to reassign? thanks!

@parasharrajat

Copy link
Copy Markdown
Member

yes, I will check it today.

@jmusial

jmusial commented Dec 22, 2025

Copy link
Copy Markdown
Contributor Author

@parasharrajat any updates ?

return null;
}

SearchRouterModal.displayName = 'SearchRouterModal';

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Remove all displayName where it is same as component name.

});

const SearchRouterModalStackNavigator = createModalStackNavigator({
[SCREENS.ENABLE_PAYMENTS_ROOT]: () => require<ReactComponentModule>('../../../../components/Search/SearchRouter/SearchRouterPage').default,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

wrong screen.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

can use toggleSearch/index.native.ts convention for all changes here?

@parasharrajat

Copy link
Copy Markdown
Member

Search has backend error https://expensify.slack.com/archives/C049HHMV9SM/p1766421823508669. Can't test this ATM.

@parasharrajat

Copy link
Copy Markdown
Member

NOTE: Slide to close does not work anymore on the search page.

@parasharrajat

Copy link
Copy Markdown
Member

Overall looks good and work as mentioned in test steps. There are some pending comments above.

@parasharrajat

Copy link
Copy Markdown
Member

Bumping @jmusial if you are back to work.

@jmusial

jmusial commented Jan 7, 2026

Copy link
Copy Markdown
Contributor Author

@parasharrajat back today, will take a look later in the evening

@parasharrajat parasharrajat Jan 8, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

this one too. the file path needs to be changed as well.

@jmusial

jmusial commented Jan 8, 2026

Copy link
Copy Markdown
Contributor Author

NOTE: Slide to close does not work anymore on the search page.

Looking into this now, looks fine on android, checking ios

EDIT:

@parasharrajat works for me here, do you have set of repro steps for the scenario it didn't work for you ?

Screen.Recording.2026-01-08.at.14.27.20.mov

@jmusial
jmusial requested a review from parasharrajat January 8, 2026 14:12
@parasharrajat

parasharrajat commented Jan 8, 2026

Copy link
Copy Markdown
Member

@jmusial I see. May be I wasn't trying the gesture properly.

@parasharrajat

Copy link
Copy Markdown
Member

@mountiny Can you please trigger adHoc build?

@github-actions

github-actions Bot commented Jan 8, 2026

Copy link
Copy Markdown
Contributor

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

@github-actions

github-actions Bot commented Jan 8, 2026

Copy link
Copy Markdown
Contributor

@jmusial

jmusial commented Jan 9, 2026

Copy link
Copy Markdown
Contributor Author

@jmusial I see. May be I wasn't trying the gesture properly.

Yeah, it's tricky exp on IOS, you need to start the gesture really far left for it to work

@parasharrajat

parasharrajat commented Jan 11, 2026

Copy link
Copy Markdown
Member

Screenshots

🔲 iOS / native

ScreenRecording_01-11-2026.23-40-58_1.mov

🔲 iOS / Safari

12.01.2026_00.01.00_REC.mp4

🔲 MacOS / Chrome

11.01.2026_23.59.19_REC.mp4

🔲 Android / Chrome

12.01.2026_00.10.42_REC.mp4

🔲 Android / native

12.01.2026_00.06.17_REC.mp4

@parasharrajat parasharrajat left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

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 tests pass on all platforms & I tested again on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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 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)
  • 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.js or at the top of the file that uses the constant) are defined as such
  • 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 form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label 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.
  • 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.

🎀 👀 🎀 C+ reviewed

@melvin-bot
melvin-bot Bot requested a review from mountiny January 11, 2026 18:42

@mountiny mountiny 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.

Thanks, lets be on a look out for any regressions and blockers please

@mountiny
mountiny merged commit c440741 into Expensify:main Jan 12, 2026
31 checks passed
@OSBotify

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

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.3.0-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/francoisl in version: 9.3.0-8 🚀

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

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.

6 participants