Skip to content

docs(dotnet): document .NET native options for Android and Apple#16664

Open
jamescrosswell wants to merge 2 commits intomasterfrom
native-options
Open

docs(dotnet): document .NET native options for Android and Apple#16664
jamescrosswell wants to merge 2 commits intomasterfrom
native-options

Conversation

@jamescrosswell
Copy link
Collaborator

DESCRIBE YOUR PR

Documents the options.Native.* configuration surface for the embedded native SDKs in .NET for Android and .NET for Apple.

Previously these options were undocumented. This adds dedicated reference pages for both platforms.

Changes:

  • New: docs/platforms/dotnet/guides/android/configuration/native-options.mdx
  • New: docs/platforms/dotnet/guides/apple/configuration/native-options.mdx
  • Updated: Android, Apple, and MAUI guide index pages to link to the new docs

Closes #11745

IS YOUR CHANGE URGENT?

  • None: Not urgent, can wait up to 1 week+

PRE-MERGE CHECKLIST

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs
  • PR was reviewed and approved by a member of the Sentry docs team

jamescrosswell and others added 2 commits March 4, 2026 13:30
Add dedicated reference pages for options.Native.* configuration on .NET
for Android and .NET for Apple platforms (iOS, macOS, Mac Catalyst).

- docs/platforms/dotnet/guides/android/configuration/native-options.mdx
- docs/platforms/dotnet/guides/apple/configuration/native-options.mdx

Covers: ANR detection, breadcrumbs, performance tracing, screenshots,
app hangs, swizzling, session replay (experimental), error handling,
NDK, networking, stack trace filtering, and profiling.

Also updates the Android, Apple, and MAUI guide index pages to link to
the new native options reference docs.

Closes #11745

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Mar 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sentry-docs Ready Ready Preview, Comment Mar 4, 2026 1:12am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
develop-docs Ignored Ignored Mar 4, 2026 1:12am

Request Review

@codeowner-assignment codeowner-assignment bot requested a review from a team March 4, 2026 01:06
Comment on lines +1 to +10
---
title: Apple Native Options
description: "Configure the embedded Sentry Cocoa SDK when using .NET for iOS, macOS, or Mac Catalyst."
sidebar_order: 10
---

When you use the .NET for Apple platforms integration, Sentry embeds the [Sentry Cocoa SDK](/platforms/apple/) to provide native crash reporting and other platform-specific features. The `options.Native` property exposes configuration for this embedded SDK.

```csharp
SentrySdk.Init(options =>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The documentation for Native.EnableAppHangTracking incorrectly lists its default value as false, while the underlying Cocoa SDK defaults it to true, potentially misleading developers.
Severity: HIGH

Suggested Fix

In the docs/platforms/dotnet/guides/apple/configuration/native-options.mdx file, change the documented defaultValue for the Native.EnableAppHangTracking option from "false" to "true" to match the actual default behavior of the Sentry Cocoa SDK.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: docs/platforms/dotnet/guides/apple/configuration/native-options.mdx#L1-L10

Potential issue: The documentation for Apple native options in `native-options.mdx`
incorrectly states that the `defaultValue` for `Native.EnableAppHangTracking` is
`false`. This contradicts the behavior of the underlying Sentry Cocoa SDK, which enables
this feature by default in versions 8.0.0 and later. This discrepancy can mislead
developers into thinking the feature is off by default. A developer might then
explicitly set the option to `false` to disable what they believe is an inactive
feature, inadvertently turning off an important, enabled-by-default monitoring
capability and leading to a loss of app hang event data.

Did we get this right? 👍 / 👎 to inform future reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document .NET mobile support

1 participant