[CP Staging] Fix search router styles by SzymczakJ · Pull Request #69638 · Expensify/App

SzymczakJ · 2025-09-02T09:05:45Z

Explanation of Change

Fixed Issues

$ #69639
$ #69723
PROPOSAL:

Tests

Enter Search Router
Make sure that if loading skeleton shows, then the styles are not broken(the border of it is the same as of seach input)
Make sure that Search Router styles are correct. Baseline:

4. Make sure that Search input styles are correct. Baseline:

Offline tests

QA Steps

Same as tests

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2025-09-02.at.13.17.25.mov

Android: mWeb Chrome

Screen.Recording.2025-09-02.at.13.18.47.mov

iOS: Native

Screen.Recording.2025-09-02.at.13.22.38.mov

iOS: mWeb Safari

Screen.Recording.2025-09-02.at.13.23.50.mov

MacOS: Chrome / Safari

Screen.Recording.2025-09-02.at.13.24.29.mov

MacOS: Desktop

Screen.Recording.2025-09-02.at.13.26.19.mov

SzymczakJ · 2025-09-02T13:50:40Z

FYI I also fixed the SearchAutocompleteInput bug that was around for a long time but noone noticed, caused by improper use of useAnimatedStyles in SearchAutocompleteInput.

Screen.Recording.2025-09-02.at.15.48.26.mov

Now fixed:

Screen.Recording.2025-09-02.at.15.49.55.mov

melvin-bot · 2025-09-02T14:22:57Z

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

c3024 · 2025-09-02T14:42:28Z

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
- 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 there are no new alerts related to the canBeMissing param for useOnyx
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 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 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.ts 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 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.
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

searchAndroid.mov

Android: mWeb Chrome

searchAndroidmWeb.mov

iOS: HybridApp

searchiOS.mov

iOS: mWeb Safari

searchiOSmWeb.mov

MacOS: Chrome / Safari

searchChrome.mov

MacOS: Desktop

shawnborton · 2025-09-02T14:53:11Z

Screenshots/videos look good to me from a design perspective 👍

c3024

LGTM!

mountiny

Thanks

…arch-router-styles [CP Staging] Fix search router styles (cherry picked from commit 8c78925) (cherry-picked to staging by mountiny)

OSBotify · 2025-09-03T08:57:47Z

✋ 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 · 2025-09-03T09:35:42Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.2.1-2 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2025-09-03T22:53:15Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.2.1-10 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2025-09-05T19:37:21Z

🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.1-20 🚀

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

OSBotify · 2025-09-05T20:04:30Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.2.2-0 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2025-09-09T03:07:13Z

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

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

ZhenjaHorbach · 2025-09-19T06:32:21Z

src/components/Search/SearchRouter/SearchRouter.tsx

-                        submitSearch(textInputValue);
-                        return;
-                    }
+            <View style={[{height: variables.searchTopBarHeight}, shouldUseNarrowLayout ? styles.mv3 : styles.mv2, shouldUseNarrowLayout ? styles.mh5 : styles.mh2]}>


Came from this issue
We had a small UI issue
More context here

fix search router styles

a4e82db

melvin-bot bot assigned SzymczakJ Sep 2, 2025

fix SearchAutocompleteInput color change

14176f5

SzymczakJ marked this pull request as ready for review September 2, 2025 14:22

SzymczakJ requested review from a team as code owners September 2, 2025 14:22

melvin-bot bot requested review from c3024 and removed request for a team September 2, 2025 14:22

shawnborton approved these changes Sep 2, 2025

View reviewed changes

SzymczakJ mentioned this pull request Sep 3, 2025

[Due for payment 2025-09-16] Android - Search - When opening search list, big empty space is briefly displayed on top. #69723

Closed

8 tasks

mountiny changed the title ~~Fix search router styles~~ [CP Staging] Fix search router styles Sep 3, 2025

c3024 approved these changes Sep 3, 2025

View reviewed changes

melvin-bot bot requested a review from mountiny September 3, 2025 08:40

mountiny approved these changes Sep 3, 2025

View reviewed changes

mountiny merged commit 8c78925 into Expensify:main Sep 3, 2025
23 of 24 checks passed

OSBotify pushed a commit that referenced this pull request Sep 3, 2025

Merge pull request #69638 from software-mansion-labs/@szymczak/fix-se…

2c8b1d5

…arch-router-styles [CP Staging] Fix search router styles (cherry picked from commit 8c78925) (cherry-picked to staging by mountiny)

OSBotify added the CP Staging marks PRs that have been CP'd to staging label Sep 3, 2025

OSBotify mentioned this pull request Sep 3, 2025

Deploy Checklist: New Expensify 2025-09-02 #69693

Closed

vincdargento mentioned this pull request Sep 3, 2025

[Due for payment 2025-09-16] Search - Offline indicator overlaps with skeleton loader in the search router #69801

Closed

8 tasks

jponikarchuk mentioned this pull request Sep 4, 2025

[Due for payment 2025-09-16] "Search in" is not shown in Inbox if previously searched for something in Reports tab #69837

Closed

8 tasks

melvin-bot bot mentioned this pull request Sep 9, 2025

[Due for payment 2025-09-16] SearchRouter styles are broken #69639

Closed

16 tasks

ZhenjaHorbach reviewed Sep 19, 2025

View reviewed changes

Conversation

SzymczakJ commented Sep 2, 2025 • edited by mountiny Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

SzymczakJ commented Sep 2, 2025

Uh oh!

melvin-bot bot commented Sep 2, 2025

Uh oh!

c3024 commented Sep 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

shawnborton commented Sep 2, 2025

Uh oh!

c3024 left a comment

Choose a reason for hiding this comment

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Sep 3, 2025

Uh oh!

OSBotify commented Sep 3, 2025

Uh oh!

OSBotify commented Sep 3, 2025

Uh oh!

OSBotify commented Sep 5, 2025

Uh oh!

OSBotify commented Sep 5, 2025

Uh oh!

OSBotify commented Sep 9, 2025

Uh oh!

ZhenjaHorbach Sep 19, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

SzymczakJ commented Sep 2, 2025 •

edited by mountiny

Loading

c3024 commented Sep 2, 2025 •

edited

Loading