chore: change default bottom tabs implementation to managed #3408
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kmichalikk
reviewed
Nov 20, 2025
kmichalikk
approved these changes
Nov 20, 2025
t0maboro
approved these changes
Nov 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changes default bottom tabs implementation to managed.
Bottom tabs offer 2 ways of controlling the container:
Most of the libraries consuming
react-native-screensuse managed tabs: expo-router and react-navigation.Changes
RNS_CONTROLLED_BOTTOM_TABS_DEFAULTtofalseTest code and steps to reproduce
Run
TestBottomTabs. Verify that managed implementation is used (use heavy render and switch between Tab1 and Tab2, selected tab should change immediately).Checklist