Skip to content

feat(native): add view hierarchy docs #13191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -56,3 +56,13 @@ Alternately, attachments also appear in the _Attachments_ tab on the **Issue Det
<Include name="common-imgs/attachments-list-example" />

If you chose to limit the number of crash reports per issue, you can show _Only Crash Reports_. This removes all other attachments from the list, which can be useful if the issue has accumulated a large number of events.

## Attaching view hierarchy

<PlatformContent includePath="enriching-events/attach-viewhierarchy" />

<Alert> The file must have the exact name `view-hierachy.json`, as described in [RFC#33](https://github.com/getsentry/rfcs/blob/main/text/0033-view-hierarchy.md). </Alert>

Along with the file appearing in the _Attachments_ tab, it is visualized on the issue as such:

<Include name="common-imgs/viewhierarchy-example" />
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
To add a view hierarchy attachment, the path to the file has to be configured when initializing the SDK. It will monitor the file and upload it along with any event or crash that is sent to Sentry:

```c
sentry_options_add_view_hierarchy(options, "./view-hierarchy.json");
```