fix: Tab bar remains visible when opening search from Reports page (mobile)

[dmkt9]

Explanation of Change

Fixed Issues

$ #88724
PROPOSAL:

Tests

Same as QA Steps

• Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

1. Open the application on a mobile device.
2. Navigate to Reports.
3. Tap the search input field.
4. Verify that the navigation bar is hidden while the search route is open.

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

android.hybrid.mp4

Android: mWeb Chrome

android.chrome.mp4

iOS: Native

ios.hybrid.mp4

iOS: mWeb Safari

ios.safari.mp4

MacOS: Chrome / Safari

mac.safari.mp4

[github-actions]

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

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #88726.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-4c39908-4bd953c-f76040d5c17f573289abd0dabf902254cd98cf44/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-4c39908-4bd953c-cf1354dd031962d71fdfca0426d546d626418ed6/index.html

Web 🕸️
https://88726.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[sumo-slonik]

@dmkt9 It looks good to me, but won’t this cause the tab bar to flicker in the flow: inbox → report → report details (RHP) → go to workspace? We should end up on the workspace initial page with the tab navigation bar without any flickering of the tab nav bar.

I would also make sure there’s no flicker between tabs when quickly switching screens.

[melvin-bot]

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

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

[dmkt9]

@dmkt9 It looks good to me, but won’t this cause the tab bar to flicker in the flow: inbox → report → report details (RHP) → go to workspace? We should end up on the workspace initial page with the tab navigation bar without any flickering of the tab nav bar.

I would also make sure there’s no flicker between tabs when quickly switching screens.

@sumo-slonik Let me check. But I don't think it will, because the changes don't affect that flow.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4c399082f2

ℹ️ 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".

[dmkt9]

@sumo-slonik I found a bug where the navigation bar disappears after the workspace route finishes loading. Is this the bug you referred to? It occurs independently of this PR:

test.mp4

[sumo-slonik]

I found a bug where the navigation bar disappears after the workspace route finishes loading. Is this the bug you referred to? It occurs independently of this PR:

Could you check whether this was also happening on the ad hoc build from the PR to the tab navigator? I think it was working correctly there.

[dmkt9]

I found a bug where the navigation bar disappears after the workspace route finishes loading. Is this the bug you referred to? It occurs independently of this PR:

Could you check whether this was also happening on the ad hoc build from the PR to the tab navigator? I think it was working correctly there.

Yes, I can reproduce the issue on that ad hoc build

[sumo-slonik]

I was pretty sure it wasn’t reproducing. In that case, it looks like we may need to show the tab nav bar not only in src/components/Navigation/TabBarBottomContent/index.native.tsx, but also in the non-native implementation (src/components/Navigation/TabBarBottomContent/index.tsx) instead of returning return <View style={styles.bottomTabBarSpacer} />;.

Could you add that to the PR as well? Once that’s in, I think the PR should be ready to merge.

[sumo-slonik]

I was pretty sure it wasn’t reproducing. In that case, it looks like we may need to show the tab nav bar not only in src/components/Navigation/TabBarBottomContent/index.native.tsx, but also in the non-native implementation (src/components/Navigation/TabBarBottomContent/index.tsx) instead of returning return <View style={styles.bottomTabBarSpacer} />;.

Could you add that to the PR as well? Once that’s in, I think the PR should be ready to merge.

It seems to me that now we may not need to split this component into native and web anymore.

[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 Δ
...omponents/Navigation/TabBarBottomContent/index.tsx	100.00% <100.00%> (+100.00%)	⬆️
...gation/AppNavigator/Navigators/TabNavigatorBar.tsx	91.30% <100.00%> (ø)
src/pages/Search/SearchPageNarrow/index.tsx	78.46% <100.00%> (+0.33%)	⬆️
...nts/Search/SearchPageHeader/useSearchPageInput.tsx	61.11% <0.00%> (-1.75%)	⬇️
... and 109 files with indirect coverage changes

[dmkt9]

I was pretty sure it wasn’t reproducing. In that case, it looks like we may need to show the tab nav bar not only in src/components/Navigation/TabBarBottomContent/index.native.tsx, but also in the non-native implementation (src/components/Navigation/TabBarBottomContent/index.tsx) instead of returning return <View style={styles.bottomTabBarSpacer} />;.
Could you add that to the PR as well? Once that’s in, I think the PR should be ready to merge.

It seems to me that now we may not need to split this component into native and web anymore.

@sumo-slonik I have updated that in commit 90ed716

However, the issue I previously reported still persists even after applying your patch. Should I report it as a separate issue, as it seems unrelated to this one?

2026-04-25.10-12-48.mp4