| id | native-stack-navigator |
|---|---|
| title | Native Stack Navigator |
| sidebar_label | Native Stack |
Native Stack Navigator provides a way for your app to transition between screens where each new screen is placed on top of a stack.
This navigator uses the native APIs UINavigationController on iOS and Fragment on Android so that navigation built with createNativeStackNavigator will behave exactly the same and have the same performance characteristics as apps built natively on top of those APIs. It also offers basic Web support using react-native-web.
One thing to keep in mind is that while @react-navigation/native-stack offers native performance and exposes native features such as large title on iOS etc., it may not be as customizable as @react-navigation/stack depending on your needs. So if you need more customization than what's possible in this navigator, consider using @react-navigation/stack instead - which is a more customizable JavaScript based implementation.
To use this navigator, ensure that you have @react-navigation/native and its dependencies (follow this guide), then install @react-navigation/native-stack:
npm install @react-navigation/native-stack💡 If you encounter any bugs while using
createNativeStackNavigator, please open issues onreact-native-screensrather than thereact-navigationrepository!
To use this navigator, import it from @react-navigation/native-stack:
import { createNativeStackNavigator } from '@react-navigation/native-stack';
const Stack = createNativeStackNavigator();
function MyStack() {
return (
<Stack.Navigator>
<Stack.Screen name="Home" component={Home} />
<Stack.Screen name="Notifications" component={Notifications} />
<Stack.Screen name="Profile" component={Profile} />
<Stack.Screen name="Settings" component={Settings} />
</Stack.Navigator>
);
}The Stack.Navigator component accepts following props:
The name of the route to render on first load of the navigator.
Default options to use for the screens in the navigator.
The following options can be used to configure the screens in the navigator:
String that can be used as a fallback for headerTitle.
Whether the back button is visible in the header. You can use it to show a back button alongside headerLeft if you have specified it.
This will have no effect on the first screen in the stack.
Title string used by the back button on iOS. Defaults to the previous scene's title, or "Back" if there's not enough space. Use headerBackTitleVisible: false to hide it.
Only supported on iOS.
Whether the back button title should be visible or not.
Only supported on iOS.
Style object for header back title. Supported properties:
fontFamilyfontSize
Only supported on iOS.
Image to display in the header as the icon in the back button. Defaults to back icon image for the platform
- A chevron on iOS
- An arrow on Android
Style of the header when a large title is shown. The large title is shown if headerLargeTitle is true and the edge of any scrollable content reaches the matching edge of the header.
Supported properties:
- backgroundColor
Only supported on iOS.
Whether to enable header with large title which collapses to regular header on scroll.
For large title to collapse on scroll, the content of the screen should be wrapped in a scrollable view such as ScrollView or FlatList. If the scrollable area doesn't fill the screen, the large title won't collapse on scroll.
Only supported on iOS.
Whether drop shadow of header is visible when a large title is shown.
Style object for large title in header. Supported properties:
fontFamilyfontSizefontWeightcolor
Only supported on iOS.
Whether to show the header. The header is shown by default. Setting this to false hides the header.
Style object for header. Supported properties:
backgroundColor
Whether to hide the elevation shadow (Android) or the bottom border (iOS) on the header.
Boolean indicating whether the navigation bar is translucent.
Defaults to false. Setting this to true makes the header absolutely positioned - so that the header floats over the screen so that it overlaps the content underneath, and changes the background color to transparent unless specified in headerStyle.
This is useful if you want to render a semi-transparent header or a blurred background.
Note that if you don't want your content to appear under the header, you need to manually add a top margin to your content. React Navigation won't do it automatically.
To get the height of the header, you can use HeaderHeightContext with React's Context API or useHeaderHeight.
Blur effect for the translucent header. The headerTransparent option needs to be set to true for this to work.
Supported values:
extraLightlightdarkregularprominentsystemUltraThinMaterialsystemThinMaterialsystemMaterialsystemThickMaterialsystemChromeMaterialsystemUltraThinMaterialLightsystemThinMaterialLightsystemMaterialLightsystemThickMaterialLightsystemChromeMaterialLightsystemUltraThinMaterialDarksystemThinMaterialDarksystemMaterialDarksystemThickMaterialDarksystemChromeMaterialDark'
Only supported on iOS.
Tint color for the header. Changes the color of back button and title.
Function which returns a React Element to display on the left side of the header. This replaces the back button. See headerBackVisible to show the back button along side left element.
Function which returns a React Element to display on the right side of the header.
String or a function that returns a React Element to be used by the header. Defaults to title or name of the screen.
When a function is passed, it receives tintColor andchildren in the options object as an argument. The title string is passed in children.
Note that if you render a custom element by passing a function, animations for the title won't work.
How to align the header title. Possible values:
leftcenter
Defaults to left on platforms other than iOS.
Not supported on iOS. It's always center on iOS and cannot be changed.
Style object for header title. Supported properties:
fontFamilyfontSizefontWeightcolor
Options to render a native search bar on iOS. Search bars are rarely static so normally it is controlled by passing an object to headerSearchBarOptions navigation option in the component's body.
Search bar is only supported on iOS.
Example:
React.useEffect(() => {
navigation.setOptions({
headerSearchBarOptions: {
// search bar options
}
});
}, [navigation]);Supported properties are described below.
Controls whether the text is automatically auto-capitalized as it is entered by the user. Possible values:
nonewordssentencescharacters
Defaults to sentences.
The search field background color.
By default bar tint color is translucent.
Boolean indicating whether to hide the navigation bar during searching.
Defaults to true.
Boolean indicating whether to hide the search bar when scrolling.
Defaults to true.
Boolean indicating whether to obscure the underlying content with semi-transparent overlay.
Defaults to true.
A callback that gets called when search bar has lost focus.
A callback that gets called when the cancel button is pressed.
A callback that gets called when the text changes. It receives the current text value of the search bar.
Example:
const [search, setSearch] = React.useState('');
React.useEffect(() => {
navigation.setOptions({
headerSearchBar: {
onChangeText: (event) => setSearch(event.nativeEvent.text),
}
});
}, [navigation]);Custom header to use instead of the default header.
This accepts a function that returns a React Element to display as a header. The function receives an object containing the following properties as the argument:
navigation- The navigation object for the current screen.route- The route object for the current screen.options- The options for the current screenback- Options for the back button, contains an object with atitleproperty to use for back button label.
Example:
import { getHeaderTitle } from '@react-navigation/elements';
// ..
header: ({ navigation, route, options, back }) => {
const title = getHeaderTitle(options, route.name);
return (
<MyHeader
title={title}
leftButton={
back ? <MyBackButton onPress={navigation.goBack} /> : undefined
}
style={options.headerStyle}
/>
);
};To set a custom header for all the screens in the navigator, you can specify this option in the screenOptions prop of the navigator.
Note that if you specify a custom header, the native functionality such as large title, search bar etc. won't work.
Sets the status bar animation (similar to the StatusBar component).
Requires setting View controller-based status bar appearance -> YES (or removing the config) in your Info.plist file.
Only supported on iOS.
statusBarHidden
Whether the status bar should be hidden on this screen.
Requires setting View controller-based status bar appearance -> YES (or removing the config) in your Info.plist file.
Only supported on iOS.
Sets the status bar color (similar to the StatusBar component).
Requires setting View controller-based status bar appearance -> YES (or removing the config) in your Info.plist file.
Only supported on iOS.
Style object for the scene content.
Whether you can use gestures to dismiss this screen. Defaults to true. Only supported on iOS.
The type of animation to use when this screen replaces another screen. Defaults to pop.
Supported values:
push: the new screen will perform push animation.pop: the new screen will perform pop animation.
How the screen should animate when pushed or popped.
Supported values:
default: use the platform default animationfade: fade screen in or outflip: flip the screen, requires stackPresentation: "modal" (iOS only)slide_from_right: slide in the new screen from right (Android only, uses default animation on iOS)slide_from_left: slide in the new screen from left (Android only, uses default animation on iOS)none: don't animate the screen
Only supported on Android and iOS.
How should the screen be presented.
Supported values:
card: the new screen will be pushed onto a stack, which means the default animation will be slide from the side on iOS, the animation on Android will vary depending on the OS version and theme.modal: the new screen will be presented modally. this also allows for a nested stack to be rendered inside the screen.transparentModal: the new screen will be presented modally, but in addition, the previous screen will stay so that the content below can still be seen if the screen has translucent background.containedModal: will use "UIModalPresentationCurrentContext" modal style on iOS and will fallback to "modal" on Android.containedTransparentModal: will use "UIModalPresentationOverCurrentContext" modal style on iOS and will fallback to "transparentModal" on Android.fullScreenModal: will use "UIModalPresentationFullScreen" modal style on iOS and will fallback to "modal" on Android.formSheet: will use "UIModalPresentationFormSheet" modal style on iOS and will fallback to "modal" on Android.
Only supported on Android and iOS.
The display orientation to use for the screen.
Supported values:
default- resolves to "all" without "portrait_down" on iOS. On Android, this lets the system decide the best orientation.all: all orientations are permitted.portrait: portrait orientations are permitted.portrait_up: right-side portrait orientation is permitted.portrait_down: upside-down portrait orientation is permitted.landscape: landscape orientations are permitted.landscape_left: landscape-left orientation is permitted.landscape_right: landscape-right orientation is permitted.
Only supported on Android and iOS.
The navigator can emit events on certain actions. Supported events are:
This event is fired when the transition animation starts for the current screen.
Event data:
e.data.closing- Boolean indicating whether the screen is being opened or closed.
Example:
React.useEffect(() => {
const unsubscribe = navigation.addListener('transitionStart', (e) => {
// Do something
});
return unsubscribe;
}, [navigation]);This event is fired when the transition animation ends for the current screen.
Event data:
e.data.closing- Boolean indicating whether the screen was opened or closed.
Example:
React.useEffect(() => {
const unsubscribe = navigation.addListener('transitionEnd', (e) => {
// Do something
});
return unsubscribe;
}, [navigation]);The native stack navigator adds the following methods to the navigation prop:
Pushes a new screen to top of the stack and navigate to it. The method accepts following arguments:
name- string - Name of the route to push onto the stack.params- object - Screen params to pass to the destination route.
navigation.push('Profile', { owner: 'Michaś' });Pops the current screen from the stack and navigates back to the previous screen. It takes one optional argument (count), which allows you to specify how many screens to pop back by.
navigation.pop();Pops all of the screens in the stack except the first one and navigates to it.
navigation.popToTop();import { createNativeStackNavigator } from '@react-navigation/native-stack';
const Stack = createNativeStackNavigator();
function MyStack() {
return (
<Stack.Navigator
initialRouteName="Home"
screenOptions={{
headerTintColor: 'white',
headerStyle: { backgroundColor: 'tomato' },
}}
>
<Stack.Screen
name="Home"
component={Home}
options={{
title: 'Awesome app',
}}
/>
<Stack.Screen
name="Profile"
component={Profile}
options={{
title: 'My profile',
}}
/>
<Stack.Screen
name="Settings"
component={Settings}
options={{
gestureEnabled: false,
}}
/>
</Stack.Navigator>
);
}