Disable Integrations

Learn more about the methods that disable integrations.

All of Sentry’s SDKs provide integrations, which extend functionality of the SDK. Most integrations are enabled by default, though you can disable them if needed.

Most integrations can be disabled via the options when initializing the SDK. For example, to disable the automatic capture of unhandled exceptions:

Copied
// Add it to your Sentry SDK initialization block:
options.DisableAppDomainUnhandledExceptionCapture()

Disables automatic capture of unhandled exceptions.

Disables automatic capture of unhandled exceptions on iOS.

The AppDomainUnhandledException handler does not reliably capture unhandled exceptions on iOS. Instead, Runtime.MarshalManagedException is used to capture unhandled exceptions on iOS.

Disables automatic capture of Unobserved Task Exceptions.

Disables adding the list of .NET Frameworks installations into events.

Disables flushing events upon AppDomain.ProcessExit event handler.

On many platforms, the .NET SDK for Sentry includes Sentry Native, which lets you capture crash reports for native (unmanaged) code. If you are experiencing difficulties, you can disable Sentry Native by setting the SentryNative build property to false:

Copied
<PropertyGroup>
  <SentryNative>false</SentryNative>
</PropertyGroup>

Note: Sentry Native is disabled by default for applications targeting WASM.

Was this helpful?
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").