Skip to content

Remove Android native tabs when React removes them - #105020

Merged
mountiny merged 14 commits into
Expensify:mainfrom
wildan-m:wildan/104505-android-tab-screen-removals
Oct 31, 2026
Merged

mountiny merged 14 commits into
Expensify:mainfrom
wildan-m:wildan/104505-android-tab-screen-removals

Conversation

@wildan-m

@wildan-m wildan-m commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

On Android, the app could crash with Maximum number of items supported by CustomBottomNavigationView is 6 when the native tab bar rebuilt its items. The tab bar never removes a tab natively: React Native checks each removal against the parent's child views before carrying it out, and the tab bar keeps its tabs in fragments rather than as child views, so every removal is silently skipped. Each time a tab was swapped in place, the old one stayed in the bar next to its replacement, and the seventh one crashed the rebuild.

This adds a react-native-screens patch that reports the tabs as the tab bar's children, the same way the library's stack already reports its screens, so removals go through. It is the same change as the open upstream fix, software-mansion/react-native-screens#5074 (software-mansion/react-native-screens#4812 rebased onto the current tabs layout).

Since #104595 removed the Insights beta, Account is always the tab without a bar item and nothing in the app adds or removes a tab at runtime, so current main no longer reaches this crash. The patch keeps the tab bar correct if a tab is added or removed at runtime again. The tab host remount in NativeTabLayout stays, because the native container still shows no content for a tab added after it selected its first tab, and still crashes when the selected tab is removed in place (upstream software-mansion/react-native-screens#4904 covers part of that). Its comment now says so, and a Jest test covers the remount.

Upstream PR: software-mansion/react-native-screens#5074

Fixed Issues

$ #104505
PROPOSAL: #104505 (comment)

Tests

Since #104595, nothing in the app adds or removes a tab at runtime, so seeing the patch at work takes a dev build with two temporary edits.

  1. In useNativeTabNavigator.ts, let Debug mode pick the tab without a bar item. Replace const tabWithoutBarItem = NAVIGATORS.SETTINGS_SPLIT_NAVIGATOR; with:
    const [isDebugModeEnabled] = useOnyx(ONYXKEYS.IS_DEBUG_MODE_ENABLED);
    const tabWithoutBarItem = isDebugModeEnabled ? SCREENS.INSIGHTS : NAVIGATORS.SETTINGS_SPLIT_NAVIGATOR;
  2. In NativeTabLayout.tsx, remove key={tabsWithoutBarItemKey} from the view wrapping the tabs, so the tab host is updated in place instead of remounted.
  3. On Android, stay on Home and run Onyx.merge('isDebugModeEnabled', true) in the React Native DevTools console, then Onyx.merge('isDebugModeEnabled', false). Repeat both calls twice more.
  4. Verify the bar shows five tabs after each call, with Insights and Account swapping places (Account shows as SettingsSplitNavigator, since main no longer gives it a bar label), and that nothing throws. On main, the bar shows six items after the first call (the removed tab is still there), and the second call throws Maximum number of items supported by CustomBottomNavigationView is 6.
  5. Undo both edits. Open every tab in the bar, then Account from the avatar in the top bar, and verify each one shows its page.
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests. The change is in how the native tab bar removes tabs, which does not depend on the network.

QA Steps

Since #104595, nothing in the app adds or removes a tab at runtime, so QA can only check that the tabs still work.

  1. On Android, open every tab in the bar, then Account from the avatar in the top bar.
  2. Verify each one shows its page and the app doesn't crash.
  • 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 any copy / text that was added to the app 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 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 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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

Before (main, with the Tests edits):

104505-android-postmerge2-before.mp4

After (this PR, with the Tests edits):

104505-android-postmerge2-after.mp4

This PR, unmodified:

104505-android-postmerge2-regression.mp4
Android: mWeb Chrome
video-android-mweb.mp4
iOS: Native
video-ios-native.mp4
iOS: mWeb Safari
video-ios-safari.mp4
MacOS: Chrome / Safari
video-desktop-chrome.mp4

Fabric verifies child removals through the view manager's getChildAt, and
TabsHostViewManager answered with the raw FrameLayout children, which never
contain the tab screens. Every tab screen removal was therefore silently
skipped, so remounted screens accumulated past the six-item bottom
navigation cap and the next menu rebuild on re-attach crashed. Override
getChildCount and getChildAt to answer from the rendered tab screens,
matching ScreenStackViewManager and ScreenContainerViewManager.
…id-tab-screen-removals

# Conflicts:
#	patches/react-native-screens/details.md
Fabric only asks for indexes it believes exist, but a null child makes it fall back to its usual already-removed handling instead of crashing with an out-of-bounds error. Also trims the comment on the overrides.
Native tab removals now go through, so the remount is only needed because the tab container cannot show a tab added after its first selection or drop the selected tab in place.
The merge's pre-commit hook rebuilt these bundles against outdated dependencies.
@github-actions

Copy link
Copy Markdown
Contributor

⚠️ 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. ⚠️

@wildan-m
wildan-m marked this pull request as ready for review October 26, 2026 23:05
@wildan-m
wildan-m requested review from a team as code owners October 26, 2026 23:05
@melvin-bot
melvin-bot Bot requested review from mananjadhav and removed request for a team October 26, 2026 23:05
@melvin-bot

melvin-bot Bot commented Oct 26, 2026

Copy link
Copy Markdown

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

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-26T23:20:44.734849Z 7105573 Draft marked ready
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

garrettmknight
garrettmknight previously approved these changes Oct 27, 2026

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

Looks good from a product perspective.

@mananjadhav mananjadhav left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

The code looks good. I'll work on the checklist.

@mananjadhav

Copy link
Copy Markdown
Collaborator

@mountiny @garrettmknight Can we have an adhoc build here? Best to test on a physical device too.

@mananjadhav

mananjadhav commented Oct 27, 2026 •

Copy link
Copy Markdown
Collaborator

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 any copy / text that was added to the app 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 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
    • 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
    • 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 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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-tab-count.mp4
Android: mWeb Chrome
mweb-chrome-tab-count.mov
iOS: HybridApp
ios-tab-count.MP4
iOS: mWeb Safari
mweb-safari-tab-count.MP4
MacOS: Chrome / Safari
web-tab-count.mov

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@mananjadhav mananjadhav left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

The lint failure seems to be unrelated to the PR.

@melvin-bot
melvin-bot Bot requested a review from mountiny October 28, 2026 18:54
…ts beta

Main removed the Insights beta and its getTabWithoutBarItem helper, so the
test now passes the tab without a bar item directly, and the comments no longer
mention the beta. The comment and the patch details also say whose first
selection leaves a later tab empty.
@wildan-m

Copy link
Copy Markdown
Contributor Author

@mananjadhav need re-approval after merge latest main

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

Thank you

@mountiny
mountiny merged commit 918f706 into Expensify:main Oct 31, 2026
44 of 45 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

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

@github-actions

Copy link
Copy Markdown
Contributor

@OSBotify OSBotify mentioned this pull request Nov 2, 2026
75 tasks done
@OSBotify

OSBotify commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.5.28-4 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update needed. This PR fixes an Android crash in how the native tab bar removes tabs, and users see no change in tabs, labels, or workflows.


view run

@jponikarchuk

Copy link
Copy Markdown

The Deploy Blocker issue https://github.com/Expensify/Expensify/issues/699512 is repro on all PRs. Could you please double check if it's not introduced by #105020

@mountiny

mountiny commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

I dont think this PR is relevant

@jponikarchuk

Copy link
Copy Markdown

The Deploy Blocker issue #105783 is repro on all PRs. Could you please double check if it's not introduced by #105020

@OSBotify

OSBotify commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

OSBotify commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.5.30-0 🚀

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