View Hierarchy

Sentry makes it possible to render a JSON representation of the view hierarchy of an error and includes it as an attachment.

This feature only applies to SDKs with a user interface, such as the ones for mobile and desktop applications. In some environments like native iOS, rendering the view hierarchy requires the UI thread and in the event of a crash, that might not be available. Another example where the view hierarchy might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.

Enabling View Hierarchy Attachments

View hierarchy debugging is an opt-in feature. You can enable it as shown below:

import * as Sentry from "@sentry/react-native";

  dsn: "",
  attachViewHierarchy: true,

Viewing View Hierarchy Attachments

View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the Issue Details page of that specific event.

Screenshots List Example

On the Issue Details page, you can interact with the view hierarchy attachment in a section called "View Hierarchy". This section represents the state of your application at the time of an error event. There are three displays: a tree view, wireframe, and detailed view for a selected node. You can select nodes in either the tree or the wireframe to view the properties collected by the SDK. The SDK will report on the following keys for each node in the view: alpha, visible, x, y, width, height, type, and identifier if applicable, but there may be additional values specific to the SDK. This feature can be used as an exploratory tool to debug layout issues, visualize unnecessarily rendered content, or gain a better understanding of the relationship between views.

View Hierarchy Example

View Hierarchy Mapping to React Native Components

View Hierarchy as captured by the SDK, represents the native user interface generated based on a React Native components structure. Generally, each React Element maps to a native component, but there are exception like View Flattening, as described in the React Native documentation.

Native components wrapping the app (created by React Native), are another part of View Hierarchy.


The code snippet below shows React Native and native UIKit components the way they would be included in the view hierarchy.

                                 // UIWindow
                                 // RCTRootContentView
                                 // ...
function MyComponent() {
  return (
    <View testID='id'>           // RTCView - id
      <Text>Hello World!</Text>  // RCTTextView


The code snippet below shows React Native and native Android components the way they would be included in the view hierarchy.

                                 // android.widget.LinearLayout
                                 // ...
                                 // com.facebook.react.ReactRootView
function MyComponent() {
  return (
    <View>                       // com.facebook.react.views.view.ReactViewGroup
      <Text>Hello World!</Text>  // com.facebook.react.views.text.ReactTextView
                                 // android.view.View - navigationBarBackground
                                 // android.view.View - statusBarBackground
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").