interface ScreenProps {
    accessibilityActions?: readonly Readonly<{
        label?: string;
        name: string;
    }>[];
    accessibilityElementsHidden?: boolean;
    accessibilityHint?: string;
    accessibilityIgnoresInvertColors?: boolean;
    accessibilityLabel?: string;
    accessibilityLabelledBy?: string | string[];
    accessibilityLanguage?: string;
    accessibilityLiveRegion?: "none" | "polite" | "assertive";
    accessibilityRole?: AccessibilityRole;
    accessibilityState?: AccessibilityState;
    accessibilityValue?: AccessibilityValue;
    accessibilityViewIsModal?: boolean;
    accessible?: boolean;
    active?: 0 | 1 | AnimatedInterpolation<number>;
    activityState?: 0 | 1 | 2 | AnimatedInterpolation<number>;
    aria-busy?: boolean;
    aria-checked?: boolean | "mixed";
    aria-disabled?: boolean;
    aria-expanded?: boolean;
    aria-hidden?: boolean;
    aria-label?: string;
    aria-labelledby?: string;
    aria-live?: "off" | "polite" | "assertive";
    aria-modal?: boolean;
    aria-selected?: boolean;
    aria-valuemax?: number;
    aria-valuemin?: number;
    aria-valuenow?: number;
    aria-valuetext?: string;
    children?: ReactNode;
    collapsable?: boolean;
    collapsableChildren?: boolean;
    customAnimationOnSwipe?: boolean;
    enabled?: boolean;
    focusable?: boolean;
    freezeOnBlur?: boolean;
    fullScreenSwipeEnabled?: boolean;
    gestureEnabled?: boolean;
    gestureResponseDistance?: GestureResponseDistanceType;
    hasLargeHeader?: boolean;
    hasTVPreferredFocus?: boolean;
    hideKeyboardOnSwipe?: boolean;
    hitSlop?: null | number | Insets;
    homeIndicatorHidden?: boolean;
    id?: string;
    importantForAccessibility?: "auto" | "yes" | "no" | "no-hide-descendants";
    isNativeStack?: boolean;
    isTVSelectable?: boolean;
    nativeBackButtonDismissalEnabled?: boolean;
    nativeID?: string;
    navigationBarColor?: ColorValue;
    navigationBarHidden?: boolean;
    needsOffscreenAlphaCompositing?: boolean;
    onAccessibilityAction?: ((event) => void);
    onAccessibilityEscape?: (() => void);
    onAccessibilityTap?: (() => void);
    onAppear?: ((e) => void);
    onComponentRef?: ((view) => void);
    onDisappear?: ((e) => void);
    onDismissed?: ((e) => void);
    onGestureCancel?: ((e) => void);
    onHeaderBackButtonClicked?: (() => void);
    onHeaderHeightChange?: ((e) => void);
    onLayout?: ((event) => void);
    onMagicTap?: (() => void);
    onMoveShouldSetResponder?: ((event) => boolean);
    onMoveShouldSetResponderCapture?: ((event) => boolean);
    onNativeDismissCancelled?: ((e) => void);
    onPointerCancel?: ((event) => void);
    onPointerCancelCapture?: ((event) => void);
    onPointerDown?: ((event) => void);
    onPointerDownCapture?: ((event) => void);
    onPointerEnter?: ((event) => void);
    onPointerEnterCapture?: ((event) => void);
    onPointerLeave?: ((event) => void);
    onPointerLeaveCapture?: ((event) => void);
    onPointerMove?: ((event) => void);
    onPointerMoveCapture?: ((event) => void);
    onPointerUp?: ((event) => void);
    onPointerUpCapture?: ((event) => void);
    onResponderEnd?: ((event) => void);
    onResponderGrant?: ((event) => void);
    onResponderMove?: ((event) => void);
    onResponderReject?: ((event) => void);
    onResponderRelease?: ((event) => void);
    onResponderStart?: ((event) => void);
    onResponderTerminate?: ((event) => void);
    onResponderTerminationRequest?: ((event) => boolean);
    onStartShouldSetResponder?: ((event) => boolean);
    onStartShouldSetResponderCapture?: ((event) => boolean);
    onTouchCancel?: ((event) => void);
    onTouchEnd?: ((event) => void);
    onTouchEndCapture?: ((event) => void);
    onTouchMove?: ((event) => void);
    onTouchStart?: ((event) => void);
    onTransitionProgress?: ((e) => void);
    onWillAppear?: ((e) => void);
    onWillDisappear?: ((e) => void);
    pointerEvents?: "box-none" | "none" | "box-only" | "auto";
    preventNativeDismiss?: boolean;
    ref?: Ref<View>;
    removeClippedSubviews?: boolean;
    renderToHardwareTextureAndroid?: boolean;
    replaceAnimation?: ScreenReplaceTypes;
    role?: Role;
    screenOrientation?: ScreenOrientationTypes;
    sheetAllowedDetents?: SheetDetentTypes;
    sheetCornerRadius?: number;
    sheetExpandsWhenScrolledToEdge?: boolean;
    sheetGrabberVisible?: boolean;
    sheetLargestUndimmedDetent?: SheetDetentTypes;
    shouldRasterizeIOS?: boolean;
    stackAnimation?: StackAnimationTypes;
    stackPresentation?: StackPresentationTypes;
    statusBarAnimation?: "none" | "fade" | "slide";
    statusBarColor?: ColorValue;
    statusBarHidden?: boolean;
    statusBarStyle?: "light" | "auto" | "inverted" | "dark";
    statusBarTranslucent?: boolean;
    style?: StyleProp<ViewStyle>;
    swipeDirection?: SwipeDirectionTypes;
    tabIndex?: 0 | -1;
    testID?: string;
    transitionDuration?: number;
    tvParallaxMagnification?: number;
    tvParallaxShiftDistanceX?: number;
    tvParallaxShiftDistanceY?: number;
    tvParallaxTiltAngle?: number;
}

Hierarchy (view full)

Properties

accessibilityActions? accessibilityElementsHidden? accessibilityHint? accessibilityIgnoresInvertColors? accessibilityLabel? accessibilityLabelledBy? accessibilityLanguage? accessibilityLiveRegion? accessibilityRole? accessibilityState? accessibilityValue? accessibilityViewIsModal? accessible? active? activityState? aria-busy? aria-checked? aria-disabled? aria-expanded? aria-hidden? aria-label? aria-labelledby? aria-live? aria-modal? aria-selected? aria-valuemax? aria-valuemin? aria-valuenow? aria-valuetext? children? collapsable? collapsableChildren? customAnimationOnSwipe? enabled? focusable? freezeOnBlur? fullScreenSwipeEnabled? gestureEnabled? gestureResponseDistance? hasLargeHeader? hasTVPreferredFocus? hideKeyboardOnSwipe? hitSlop? homeIndicatorHidden? id? importantForAccessibility? isNativeStack? isTVSelectable? nativeBackButtonDismissalEnabled? nativeID? navigationBarColor? navigationBarHidden? needsOffscreenAlphaCompositing? onAccessibilityAction? onAccessibilityEscape? onAccessibilityTap? onAppear? onComponentRef? onDisappear? onDismissed? onGestureCancel? onHeaderBackButtonClicked? onHeaderHeightChange? onLayout? onMagicTap? onMoveShouldSetResponder? onMoveShouldSetResponderCapture? onNativeDismissCancelled? onPointerCancel? onPointerCancelCapture? onPointerDown? onPointerDownCapture? onPointerEnter? onPointerEnterCapture? onPointerLeave? onPointerLeaveCapture? onPointerMove? onPointerMoveCapture? onPointerUp? onPointerUpCapture? onResponderEnd? onResponderGrant? onResponderMove? onResponderReject? onResponderRelease? onResponderStart? onResponderTerminate? onResponderTerminationRequest? onStartShouldSetResponder? onStartShouldSetResponderCapture? onTouchCancel? onTouchEnd? onTouchEndCapture? onTouchMove? onTouchStart? onTransitionProgress? onWillAppear? onWillDisappear? pointerEvents? preventNativeDismiss? ref? removeClippedSubviews? renderToHardwareTextureAndroid? replaceAnimation? role? screenOrientation? sheetAllowedDetents? sheetCornerRadius? sheetExpandsWhenScrolledToEdge? sheetGrabberVisible? sheetLargestUndimmedDetent? shouldRasterizeIOS? stackAnimation? stackPresentation? statusBarAnimation? statusBarColor? statusBarHidden? statusBarStyle? statusBarTranslucent? style? swipeDirection? tabIndex? testID? transitionDuration? tvParallaxMagnification? tvParallaxShiftDistanceX? tvParallaxShiftDistanceY? tvParallaxTiltAngle?

Properties

accessibilityActions?: readonly Readonly<{
    label?: string;
    name: string;
}>[]

Provides an array of custom actions available for accessibility.

accessibilityElementsHidden?: boolean

A Boolean value indicating whether the accessibility elements contained within this accessibility element are hidden to the screen reader.

Platform

ios

accessibilityHint?: string

An accessibility hint helps users understand what will happen when they perform an action on the accessibility element when that result is not obvious from the accessibility label.

accessibilityIgnoresInvertColors?: boolean

Platform

ios

accessibilityLabel?: string

Overrides the text that's read by the screen reader when the user interacts with the element. By default, the label is constructed by traversing all the children and accumulating all the Text nodes separated by space.

accessibilityLabelledBy?: string | string[]

Identifies the element that labels the element it is applied to. When the assistive technology focuses on the component with this props, the text is read aloud. The value should should match the nativeID of the related element.

Platform

android

accessibilityLanguage?: string

By using the accessibilityLanguage property, the screen reader will understand which language to use while reading the element's label, value and hint. The provided string value must follow the BCP 47 specification (https://www.rfc-editor.org/info/bcp47). https://reactnative.dev/docs/accessibility#accessibilitylanguage-ios

Platform

ios

accessibilityLiveRegion?: "none" | "polite" | "assertive"

Indicates to accessibility services whether the user should be notified when this view changes. Works for Android API >= 19 only.

accessibilityRole?: AccessibilityRole

Accessibility Role tells a person using either VoiceOver on iOS or TalkBack on Android the type of element that is focused on.

accessibilityState?: AccessibilityState

Accessibility State tells a person using either VoiceOver on iOS or TalkBack on Android the state of the element currently focused on.

accessibilityValue?: AccessibilityValue

Represents the current value of a component. It can be a textual description of a component's value, or for range-based components, such as sliders and progress bars, it contains range information (minimum, current, and maximum).

accessibilityViewIsModal?: boolean

A Boolean value indicating whether VoiceOver should ignore the elements within views that are siblings of the receiver.

Platform

ios

accessible?: boolean

When true, indicates that the view is an accessibility element. By default, all the touchable elements are accessible.

active?: 0 | 1 | AnimatedInterpolation<number>
activityState?: 0 | 1 | 2 | AnimatedInterpolation<number>
aria-busy?: boolean
aria-checked?: boolean | "mixed"
aria-disabled?: boolean
aria-expanded?: boolean
aria-hidden?: boolean

A value indicating whether the accessibility elements contained within this accessibility element are hidden.

aria-label?: string
aria-labelledby?: string

Identifies the element that labels the element it is applied to. When the assistive technology focuses on the component with this props, the text is read aloud. The value should should match the nativeID of the related element.

Platform

android

aria-live?: "off" | "polite" | "assertive"

Indicates to accessibility services whether the user should be notified when this view changes. Works for Android API >= 19 only.

aria-modal?: boolean
aria-selected?: boolean
aria-valuemax?: number
aria-valuemin?: number
aria-valuenow?: number
aria-valuetext?: string
children?: ReactNode
collapsable?: boolean

Views that are only used to layout their children or otherwise don't draw anything may be automatically removed from the native hierarchy as an optimization. Set this property to false to disable this optimization and ensure that this View exists in the native view hierarchy.

collapsableChildren?: boolean

Setting to false prevents direct children of the view from being removed from the native view hierarchy, similar to the effect of setting collapsable={false} on each child.

customAnimationOnSwipe?: boolean

Boolean indicating that swipe dismissal should trigger animation provided by stackAnimation. Defaults to false.

Platform

ios

enabled?: boolean

All children screens should have the same value of their "enabled" prop as their container.

focusable?: boolean

Whether this View should be focusable with a non-touch input device, eg. receive focus with a hardware keyboard.

freezeOnBlur?: boolean

Whether inactive screens should be suspended from re-rendering. Defaults to false. When enableFreeze() is run at the top of the application defaults to true.

fullScreenSwipeEnabled?: boolean

Boolean indicating whether the swipe gesture should work on whole screen. Swiping with this option results in the same transition animation as simple_push by default. It can be changed to other custom animations with customAnimationOnSwipe prop, but default iOS swipe animation is not achievable due to usage of custom recognizer. Defaults to false.

Platform

ios

gestureEnabled?: boolean

Whether you can use gestures to dismiss this screen. Defaults to true.

Platform

ios

gestureResponseDistance?: GestureResponseDistanceType

Use it to restrict the distance from the edges of screen in which the gesture should be recognized. To be used alongside fullScreenSwipeEnabled.

Platform

ios

hasLargeHeader?: boolean

Internal boolean used to detect if current header has large title on iOS.

hasTVPreferredFocus?: boolean

(Apple TV only) May be set to true to force the Apple TV focus engine to move focus to this view.

Platform

ios

hideKeyboardOnSwipe?: boolean

Whether the keyboard should hide when swiping to the previous screen. Defaults to false.

Platform

ios

hitSlop?: null | number | Insets

This defines how far a touch event can start away from the view. Typical interface guidelines recommend touch targets that are at least 30 - 40 points/density-independent pixels. If a Touchable view has a height of 20 the touchable height can be extended to 40 with hitSlop={{top: 10, bottom: 10, left: 0, right: 0}} NOTE The touch area never extends past the parent view bounds and the Z-index of sibling views always takes precedence if a touch hits two overlapping views.

homeIndicatorHidden?: boolean

Whether the home indicator should be hidden on this screen. Defaults to false.

Platform

ios

id?: string

Used to reference react managed views from native code.

importantForAccessibility?: "auto" | "yes" | "no" | "no-hide-descendants"

[Android] Controlling if a view fires accessibility events and if it is reported to accessibility services.

isNativeStack?: boolean

Internal boolean used to not attach events used only by native-stack. It prevents non native-stack navigators from sending transition progress from their Screen components.

isTVSelectable?: boolean

(Apple TV only) When set to true, this view will be focusable and navigable using the Apple TV remote.

Platform

ios

nativeBackButtonDismissalEnabled?: boolean

Boolean indicating whether, when the Android default back button is clicked, the pop action should be performed on the native side or on the JS side to be able to prevent it. Unfortunately the same behavior is not available on iOS since the behavior of native back button cannot be changed there. Defaults to false.

Platform

android

nativeID?: string

Used to reference react managed views from native code.

navigationBarColor?: ColorValue

Sets the navigation bar color. Defaults to initial status bar color.

Platform

android

navigationBarHidden?: boolean

Sets the visibility of the navigation bar. Defaults to false.

Platform

android

needsOffscreenAlphaCompositing?: boolean

Whether this view needs to rendered offscreen and composited with an alpha in order to preserve 100% correct colors and blending behavior. The default (false) falls back to drawing the component and its children with an alpha applied to the paint used to draw each element instead of rendering the full component offscreen and compositing it back with an alpha value. This default may be noticeable and undesired in the case where the View you are setting an opacity on has multiple overlapping elements (e.g. multiple overlapping Views, or text and a background).

Rendering offscreen to preserve correct alpha behavior is extremely expensive and hard to debug for non-native developers, which is why it is not turned on by default. If you do need to enable this property for an animation, consider combining it with renderToHardwareTextureAndroid if the view contents are static (i.e. it doesn't need to be redrawn each frame). If that property is enabled, this View will be rendered off-screen once, saved in a hardware texture, and then composited onto the screen with an alpha each frame without having to switch rendering targets on the GPU.

onAccessibilityAction?: ((event) => void)

When accessible is true, the system will try to invoke this function when the user performs an accessibility custom action.

Type declaration

onAccessibilityEscape?: (() => void)

When accessible is true, the system will invoke this function when the user performs the escape gesture (scrub with two fingers).

Type declaration

    • (): void
    • Returns void

Platform

ios

onAccessibilityTap?: (() => void)

When accessible is true, the system will try to invoke this function when the user performs accessibility tap gesture.

Type declaration

    • (): void
    • Returns void

Platform

ios

onAppear?: ((e) => void)

A callback that gets called when the current screen appears.

Type declaration

onComponentRef?: ((view) => void)

Type declaration

    • (view): void
    • Parameters

      • view: unknown

      Returns void

onDisappear?: ((e) => void)

A callback that gets called when the current screen disappears.

Type declaration

onDismissed?: ((e) => void)

A callback that gets called when the current screen is dismissed by hardware back (on Android) or dismiss gesture (swipe back or down). The callback takes the number of dismissed screens as an argument since iOS 14 native header back button can pop more than 1 screen at a time.

Type declaration

onGestureCancel?: ((e) => void)

A callback that gets called after swipe back is canceled.

Type declaration

onHeaderBackButtonClicked?: (() => void)

An internal callback that gets called when the native header back button is clicked on Android and enableNativeBackButtonDismissal is set to false. It dismises the screen using navigation.pop().

Type declaration

    • (): void
    • Returns void

Platform

android

onHeaderHeightChange?: ((e) => void)

A callback that gets called when the header height has changed.

Type declaration

onLayout?: ((event) => void)

Invoked on mount and layout changes with

{nativeEvent: { layout: {x, y, width, height}}}.

Type declaration

onMagicTap?: (() => void)

When accessible is true, the system will invoke this function when the user performs the magic tap gesture.

Type declaration

    • (): void
    • Returns void

Platform

ios

onMoveShouldSetResponder?: ((event) => boolean)

Called for every touch move on the View when it is not the responder: does this view want to "claim" touch responsiveness?

Type declaration

onMoveShouldSetResponderCapture?: ((event) => boolean)

onStartShouldSetResponder and onMoveShouldSetResponder are called with a bubbling pattern, where the deepest node is called first. That means that the deepest component will become responder when multiple Views return true for *ShouldSetResponder handlers. This is desirable in most cases, because it makes sure all controls and buttons are usable.

However, sometimes a parent will want to make sure that it becomes responder. This can be handled by using the capture phase. Before the responder system bubbles up from the deepest component, it will do a capture phase, firing on*ShouldSetResponderCapture. So if a parent View wants to prevent the child from becoming responder on a touch start, it should have a onStartShouldSetResponderCapture handler which returns true.

Type declaration

onNativeDismissCancelled?: ((e) => void)

An internal callback called when screen is dismissed by gesture or by native header back button and preventNativeDismiss is set to true.

Type declaration

Platform

ios

onPointerCancel?: ((event) => void)

Type declaration

onPointerCancelCapture?: ((event) => void)

Type declaration

onPointerDown?: ((event) => void)

Type declaration

onPointerDownCapture?: ((event) => void)

Type declaration

onPointerEnter?: ((event) => void)

Type declaration

onPointerEnterCapture?: ((event) => void)

Type declaration

onPointerLeave?: ((event) => void)

Type declaration

onPointerLeaveCapture?: ((event) => void)

Type declaration

onPointerMove?: ((event) => void)

Type declaration

onPointerMoveCapture?: ((event) => void)

Type declaration

onPointerUp?: ((event) => void)

Type declaration

onPointerUpCapture?: ((event) => void)

Type declaration

onResponderEnd?: ((event) => void)

If the View returns true and attempts to become the responder, one of the following will happen:

Type declaration

onResponderGrant?: ((event) => void)

The View is now responding for touch events. This is the time to highlight and show the user what is happening

Type declaration

onResponderMove?: ((event) => void)

The user is moving their finger

Type declaration

onResponderReject?: ((event) => void)

Something else is the responder right now and will not release it

Type declaration

onResponderRelease?: ((event) => void)

Fired at the end of the touch, ie "touchUp"

Type declaration

onResponderStart?: ((event) => void)

Type declaration

onResponderTerminate?: ((event) => void)

The responder has been taken from the View. Might be taken by other views after a call to onResponderTerminationRequest, or might be taken by the OS without asking (happens with control center/ notification center on iOS)

Type declaration

onResponderTerminationRequest?: ((event) => boolean)

Something else wants to become responder. Should this view release the responder? Returning true allows release

Type declaration

onStartShouldSetResponder?: ((event) => boolean)

Does this view want to become responder on the start of a touch?

Type declaration

onStartShouldSetResponderCapture?: ((event) => boolean)

onStartShouldSetResponder and onMoveShouldSetResponder are called with a bubbling pattern, where the deepest node is called first. That means that the deepest component will become responder when multiple Views return true for *ShouldSetResponder handlers. This is desirable in most cases, because it makes sure all controls and buttons are usable.

However, sometimes a parent will want to make sure that it becomes responder. This can be handled by using the capture phase. Before the responder system bubbles up from the deepest component, it will do a capture phase, firing on*ShouldSetResponderCapture. So if a parent View wants to prevent the child from becoming responder on a touch start, it should have a onStartShouldSetResponderCapture handler which returns true.

Type declaration

onTouchCancel?: ((event) => void)

Type declaration

onTouchEnd?: ((event) => void)

Type declaration

onTouchEndCapture?: ((event) => void)

Type declaration

onTouchMove?: ((event) => void)

Type declaration

onTouchStart?: ((event) => void)

Type declaration

onTransitionProgress?: ((e) => void)

An internal callback called every frame during the transition of screens of native-stack, used to feed transition context.

Type declaration

onWillAppear?: ((e) => void)

A callback that gets called when the current screen will appear. This is called as soon as the transition begins.

Type declaration

onWillDisappear?: ((e) => void)

A callback that gets called when the current screen will disappear. This is called as soon as the transition begins.

Type declaration

pointerEvents?: "box-none" | "none" | "box-only" | "auto"

In the absence of auto property, none is much like CSS's none value. box-none is as if you had applied the CSS class:

.box-none { pointer-events: none; } .box-none * { pointer-events: all; }

box-only is the equivalent of

.box-only { pointer-events: all; } .box-only * { pointer-events: none; }

But since pointerEvents does not affect layout/appearance, and we are already deviating from the spec by adding additional modes, we opt to not include pointerEvents on style. On some platforms, we would need to implement it as a className anyways. Using style or not is an implementation detail of the platform.

preventNativeDismiss?: boolean

Boolean indicating whether to prevent current screen from being dismissed. Defaults to false.

Platform

ios

ref?: Ref<View>
removeClippedSubviews?: boolean

This is a special performance property exposed by RCTView and is useful for scrolling content when there are many subviews, most of which are offscreen. For this property to be effective, it must be applied to a view that contains many subviews that extend outside its bound. The subviews must also have overflow: hidden, as should the containing view (or one of its superviews).

renderToHardwareTextureAndroid?: boolean

Whether this view should render itself (and all of its children) into a single hardware texture on the GPU.

On Android, this is useful for animations and interactions that only modify opacity, rotation, translation, and/or scale: in those cases, the view doesn't have to be redrawn and display lists don't need to be re-executed. The texture can just be re-used and re-composited with different parameters. The downside is that this can use up limited video memory, so this prop should be set back to false at the end of the interaction/animation.

replaceAnimation?: ScreenReplaceTypes

How should the screen replacing another screen animate. Defaults to pop. The following values are currently supported:

  • "push" – the new screen will perform push animation.
  • "pop" – the new screen will perform pop animation.
role?: Role

Indicates to accessibility services to treat UI component like a specific role.

screenOrientation?: ScreenOrientationTypes

In which orientation should the screen appear. The following values are currently supported:

  • "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
sheetAllowedDetents?: SheetDetentTypes

Describes heights where a sheet can rest. Works only when stackPresentation is set to formSheet. Defaults to large.

Available values:

  • large - only large detent level will be allowed
  • medium - only medium detent level will be allowed
  • all - all detent levels will be allowed

Platform

ios

sheetCornerRadius?: number

The corner radius that the sheet will try to render with. Works only when stackPresentation is set to formSheet.

If set to non-negative value it will try to render sheet with provided radius, else it will apply system default.

If left unset system default is used.

Platform

ios

sheetExpandsWhenScrolledToEdge?: boolean

Whether the sheet should expand to larger detent when scrolling. Works only when stackPresentation is set to formSheet. Defaults to true.

Platform

ios

sheetGrabberVisible?: boolean

Boolean indicating whether the sheet shows a grabber at the top. Works only when stackPresentation is set to formSheet. Defaults to false.

Platform

ios

sheetLargestUndimmedDetent?: SheetDetentTypes

The largest sheet detent for which a view underneath won't be dimmed. Works only when stackPresentation is set to formSheet.

If this prop is set to:

  • large - the view underneath won't be dimmed at any detent level
  • medium - the view underneath will be dimmed only when detent level is large
  • all - the view underneath will be dimmed for any detent level

Defaults to all.

Platform

ios

shouldRasterizeIOS?: boolean

Whether this view should be rendered as a bitmap before compositing.

On iOS, this is useful for animations and interactions that do not modify this component's dimensions nor its children; for example, when translating the position of a static view, rasterization allows the renderer to reuse a cached bitmap of a static view and quickly composite it during each frame.

Rasterization incurs an off-screen drawing pass and the bitmap consumes memory. Test and measure when using this property.

stackAnimation?: StackAnimationTypes

How the screen should appear/disappear when pushed or popped at the top of the stack. The following values are currently supported:

  • "default" – uses a platform default animation
  • "fade" – fades screen in or out
  • "fade_from_bottom" – performs a fade from bottom animation
  • "flip" – flips the screen, requires stackPresentation: "modal" (iOS only)
  • "simple_push" – performs a default animation, but without shadow and native header transition (iOS only)
  • slide_from_bottom – performs a slide from bottom animation
  • "slide_from_right" - slide in the new screen from right to left (Android only, resolves to default transition on iOS)
  • "slide_from_left" - slide in the new screen from left to right
  • "ios" - iOS like slide in animation (Android only, resolves to default transition on iOS)
  • "none" – the screen appears/dissapears without an animation
stackPresentation?: StackPresentationTypes

How should the screen be presented. The following values are currently supported:

  • "push" – the new screen will be pushed onto a stack which on iOS means that the default animation will be slide from the side, the animation on Android may vary depending on the OS version and theme.
  • "modal" – the new screen will be presented modally. In addition this allow for a nested stack to be rendered inside such screens.
  • "transparentModal" – the new screen will be presented modally but in addition the second to last screen will remain attached to the stack container such that if the top screen is non opaque the content below can still be seen. If "modal" is used instead the below screen will get unmounted as soon as the transition ends.
  • "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.
statusBarAnimation?: "none" | "fade" | "slide"

Sets the status bar animation (similar to the StatusBar component). Requires enabling (or deleting) View controller-based status bar appearance in your Info.plist file on iOS.

statusBarColor?: ColorValue

Sets the status bar color (similar to the StatusBar component). Defaults to initial status bar color.

Platform

android

statusBarHidden?: boolean

Whether the status bar should be hidden on this screen. Requires enabling (or deleting) View controller-based status bar appearance in your Info.plist file on iOS. Defaults to false.

statusBarStyle?: "light" | "auto" | "inverted" | "dark"

Sets the status bar color (similar to the StatusBar component). Requires enabling (or deleting) View controller-based status bar appearance in your Info.plist file on iOS. Defaults to auto.

statusBarTranslucent?: boolean

Sets the translucency of the status bar. Defaults to false.

Platform

android

swipeDirection?: SwipeDirectionTypes

Sets the direction in which you should swipe to dismiss the screen. When using vertical option, options fullScreenSwipeEnabled: true, customAnimationOnSwipe: true and stackAnimation: 'slide_from_bottom' are set by default. The following values are supported:

  • vertical – dismiss screen vertically
  • horizontal – dismiss screen horizontally (default)

Platform

ios

tabIndex?: 0 | -1

Indicates whether this View should be focusable with a non-touch input device, eg. receive focus with a hardware keyboard. See https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex for more details.

Supports the following values:

  • 0 (View is focusable)
  • -1 (View is not focusable)
testID?: string

Used to locate this view in end-to-end tests.

transitionDuration?: number

Changes the duration (in milliseconds) of slide_from_bottom, fade_from_bottom, fade and simple_push transitions on iOS. Defaults to 350. The duration of default and flip transitions isn't customizable.

Platform

ios

tvParallaxMagnification?: number

(Apple TV only) May be used to change the appearance of the Apple TV parallax effect when this view goes in or out of focus. Defaults to 1.0.

Platform

ios

tvParallaxShiftDistanceX?: number

(Apple TV only) May be used to change the appearance of the Apple TV parallax effect when this view goes in or out of focus. Defaults to 2.0.

Platform

ios

tvParallaxShiftDistanceY?: number

(Apple TV only) May be used to change the appearance of the Apple TV parallax effect when this view goes in or out of focus. Defaults to 2.0.

Platform

ios

tvParallaxTiltAngle?: number

(Apple TV only) May be used to change the appearance of the Apple TV parallax effect when this view goes in or out of focus. Defaults to 0.05.

Platform

ios