If no, then automatically add the integration dependency with the version of the Sentry Android SDK inferred from above. If yes, then keep the current version of the direct dependency. If no, then automatically add the sentry-android dependency with the specified sentryVersion from the plugin configuration (defaults to the latest published SDK version).Ĭheck if the module/app has a direct dependency on any of the integrations (Fragment, Timber, or OkHttp): If yes, then use the version of the direct dependency. The plugin algorithm does the following when defining dependency versions:Ĭheck if the module/app has a direct dependency on the Sentry Android SDK: Starting with version 3.1.0, the feature is enabled by default, so you don't need to add any dependencies - you just use the Sentry Gradle plugin. The plugin offers the automated installation feature of the Sentry Android SDK and the Fragment, Timber, OkHttp, and Jetpack Compose integrations. To learn more about the internals of auto-instrumentation, check out this blog post. * navigation controllers used in Jetpack Compose.Ĭheck Integrations page for more detailed explanation of each instrumentation feature. * This feature uses bytecode manipulation and adds an OnDestinationChangedListener to all * When enabled the SDK will create breadcrumbs when navigating * Only available v3.1.0 and above of the Sentry Android Gradle plugin. * Requires sentry-android SDK version 5.0.0 and above. * This feature uses bytecode manipulation and attaches SentryOkHttpInterceptor to all OkHttp * sentry-trace-header for distributed tracing. * When enabled the SDK will create spans for outgoing network requests and attach * Requires sentry-android SDK version 5.5.0 and above
* mentioned classes with Sentry-specific implementations. * This feature uses bytecode manipulation and replaces the above * When enabled the SDK will create spans for , * Requires sentry-android SDK version 4.0.0 and above
* When enabled the SDK will create spans for any CRUD operation performed by 'androidx.sqlite' You can specify which variant/flavor/build-type should be ignored by Sentry in your app/adle file: Now when you build your app, the plugin will upload the ProGuard/R8 mappings, source bundle, and native symbols as you configured them to Sentry. If disabled, all the logic // related to the dependencies metadata report will be excluded. If enabled, the plugin will collect external dependencies and // upload them to Sentry as part of events. Sentry // Disables or enables dependencies metadata reporting for Sentry.
0 kommentar(er)
