react-native-screens
4.30.0 · 13 Oct 2026MIT6.4M / weekRepositoryHomepagenpmAtom feed
Latest releases
All 124 releases4.30.0
13 Oct 2026On iOS 26,
edgesForExtendedLayout(which we used to lay out the screen below an opaque header) doesn't position the screen correctly in landscape and in modals. We partially worked around this with aSafeAreaView(#3231).On iPhone Duo (iOS 27) the same problem affects regular screens in portrait. The screen ended up partially under the header. Additionally, changes to internal hierarchy of the header introduced new bugs related to
Pressables.An opaque header's background doesn't reach the top of the screen and leaves a strip above it. When this was reported on the Apple Developer Forums, Apple didn't treat it as a bug and pointed to the guidance against custom bar backgrounds instead.
What's changed
This release focuses on iOS 27 and iPhone Duo support in Stack v4. On iOS 26+ screens are now laid out under an opaque navigation bar and inset through the safe area instead of UIKit's extended-layout frame and
useHeaderHeightreports the visible height of the bar while it is minimized. The newunstable_safeAreaEdgesprop onScreenStackItemlets a screen override the insets applied on iOS 26+, and opaque headers no longer minimize on scroll.Tabs.HostgainsprominentScreenKey(iOS 27+), backed byprominentTabIdentifier, so a chosen tab stays visible when the tab bar minimizes.iOS 26+: opaque headers in native stack (iOS)
Starting with iOS 26, Apple recommends against custom navigation bar backgrounds. Bars are transparent by default and content is meant to extend under them - see WWDC25: Build a UIKit app with the new design. Opaque headers (
headerTransparent: false) aren't deprecated, but UIKit's support for them is getting worse:On iOS 26,
edgesForExtendedLayout(which we used to lay out the screen below an opaque header) doesn't position the screen correctly in landscape and in modals. We partially worked around this with aSafeAreaView(#3231).On iPhone Duo (iOS 27) the same problem affects regular screens in portrait. The screen ended up partially under the header. Additionally, changes to internal hierarchy of the header introduced new bugs related to
Pressables.An opaque header's background doesn't reach the top of the screen and leaves a strip above it. When this was reported on the Apple Developer Forums, Apple didn't treat it as a bug and pointed to the guidance against custom bar backgrounds instead.
[!TIP]
We recommend following Apple's guidance and using a transparent header on iOS 26+.Improvements
iOS, Tabs: add
prominentScreenKeyso a chosen tab stays visible when the tab bar minimizesiOS, Stack v4: add
unstable_safeAreaEdgespropiOS, Stack v4: prevent header minimization for opaque header
Bugfixes
fix broken types being published for tabs host and screen
iOS, Stack v4: use native screen origin as shadow tree offset
iOS, Stack v4: lay out screens under an opaque navigation bar on iOS 26+
iOS, Stack v4: update header subview positions after navigation bar layout on iOS 26+
iOS, Stack v4: report minimized header height on iOS 27+ via
useHeaderHeightiOS, Tabs: don't drop user selection of UISearchTab on mount transactions
iOS, Tabs: apply async-loaded icons to tabs that overflow into More on the UITab path
iOS, Tabs: filter UIKit's didSelectTab: for programmatic selection while More is active
Android: prevent legacy and tabs containers from delaying child pressed state
4.29.0
9 Oct 2026iOS, Tabs: add
tabBarHiddenAnimationEnabledpropiOS, Tabs: add tabBarSidebarPreferredPlacement prop to choose between sidebar and tab bar on iOS 27
iOS, Tabs: Migrate to UITab API for iOS >= 26.1
What's changed
This release migrates the Tabs implementation on iOS 26.1+ to the
UITabAPI and extends theTabscomponent with several new props:tabBarHiddenAnimationEnabled,tabBarSidebarPreferredPlacement,automaticallyActivatesSearch(backed byUISearchTab) and custom drawable/symbol tab-bar icons with per-slot coloring and per-tab sizing. Header items in Stack v4 gain avisibilityPriorityprop on iOS.It also brings a number of fixes, most notably hardening of the Android fragment lifecycle (R8-safe restoration, orphaned fragment cleanup, no crash during instance teardown) and corrections to form sheet scroll view handling on iOS.
Improvements
iOS, Tabs: add
tabBarHiddenAnimationEnabledpropiOS, Tabs: add tabBarSidebarPreferredPlacement prop to choose between sidebar and tab bar on iOS 27
iOS, Tabs: Migrate to UITab API for iOS >= 26.1
iOS, Tabs: Use
UISearchTabwithautomaticallyActivatesSearchpropTabs: custom drawable/symbol tab-bar icons — per-slot coloring, per-tab size, indicator sizing, iOS fallback
iOS, Stack v4: Add
visibilityPriorityprop to header items
Bugfixes
iOS: skip form sheet scroll view frame correction once the screen is invalidated
iOS, Stack v4: stop form sheet from resizing a recycled scroll view
iOS, Stack v4: send dismiss event to js when pop animation ends
iOS, Tabs: prevent tab bar hidden animation on first render
iOS, Tabs: enforce consistent bottom accessory width
iOS, Tabs: Hide "Edit" button in sidebar for UITab API
iOS, Tabs: Reorder tab image configuration calls
Android: make fragment restoration R8-safe
Android: don't crash in setupFabric during instance teardown
Android: restore touch coordinates after covered screens rotate
Android, Stack v4: don't run header update for a screen detached from its stack
Android, Stack v4: remove orphaned fragments when ScreenContainer detaches
Android, Tabs: let touches through the strip a hidden tab bar leaves behind
4.28.0
14 Sep 2026Android, Tabs: handle forceLayout to ensure tab bar is properly laid out after configuration change
Android, Stack v4+: append SwipeRefreshLayout transition filler
Android, Tabs: use ViewIdGenerator to identify MenuItems instead of sequential ids
What's changed?
This is a small release that brings several fixes to the library.
Bugfixes
Android, Tabs: handle forceLayout to ensure tab bar is properly laid out after configuration change
Android, Stack v4+: append SwipeRefreshLayout transition filler
Android, Tabs: use ViewIdGenerator to identify MenuItems instead of sequential ids
Android, Stack v4: prevent adding preloaded and dismissed fragments when popping from opaque to translucent screen
Android, Tabs: expose tab item testID as viewIdResourceName
Example: Upgrade kotlin to 2.3.*
Android: use-after-free of RNSScreenRemovalListener registered as mounting override delegate
4.27.0
7 Aug 2026Android, Stack v5: support sending multiple updates via view command
Stack v5, iOS: Implement basic view commands for iOS header menu
experimental, iOS: add experimental ScrollToTopGuard component
What's changed
This release adds support for React Native 0.87, fixing a runtime crash on iOS in the process. It also introduces the experimental
ScrollToTopGuardcomponent and fully migrates theSplitcomponent implementation from Swift to Objective-C.Improvements
Android, Stack v5: support sending multiple updates via view command
Stack v5, iOS: Implement basic view commands for iOS header menu
experimental, iOS: add experimental ScrollToTopGuard component
ios, Stack v4: add subtitle support for UIMenu header button submenus
Bugfixes
Android: defensively guard against an unexpected menuItem Id
Android, Stack: don't add top inset to measured header height when it's disabled
iOS, Stack v4: fall back to inheriting orientation if it's not defined on the screen
iOS: Don't swap view controller's view during transition
iOS, Tabs: re-layout tab bar after async icon load to prevent label truncation on iOS 26
Android: Fix crash when header gets update during screen removal
Android, FormSheet v4: Cleanup inset and layout listener
JS: Prevent using ViewInstance type
iOS, Stack v5: use framework-style imports for React core headers
4.26.2
16 Jul 2026
Notes older than 90 days are read on the Releases tab.
Dependency tracking · free for 3 projects
Know when your own dependencies move
react-native-screens published 17 releases in the last 12 months. Inlinr folds the routine ones into a line and keeps the few that need you.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Registry facts last checked 21 Oct 2026. Releases and advisories last read 21 Oct 2026.