Update dependency io.sentry:sentry-android to v8.20.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
io.sentry:sentry-android	8.11.0 -> 8.20.0

---

Release Notes

getsentry/sentry-java (io.sentry:sentry-android)

v8.20.0

Compare Source

Fixes

• Do not use named capturing groups for regular expressions (#​4652)
  • This fixes a crash on Android versions below 8.0 (API level 26)

Features

• Add onDiscard to enable users to track the type and amount of data discarded before reaching Sentry (#​4612)
  • Stub for setting the callback on Sentry.init:

    Sentry.init(options -> {
      ...
      options.setOnDiscard(
       (reason, category, number) -> {
         // Your logic to process discarded data
       });
    });

v8.19.1

Compare Source

Fixes

• Do not store No-Op scopes onto OpenTelemetry Context when wrapping (#​4631)
  • In 8.18.0 and 8.19.0 the SDK could break when initialized too late.

v8.19.0

Compare Source

Features

• Add a isEnableSystemEventBreadcrumbsExtras option to disable reporting system events extras for breadcrumbs (#​4625)

Improvements

• Session Replay: Use main thread looper to schedule replay capture (#​4542)
• Use single LifecycleObserver and multi-cast it to the integrations interested in lifecycle states (#​4567)
• Add sentry.origin attribute to logs (#​4618)
  • This helps identify which integration captured a log event
• Prewarm SentryExecutorService for better performance at runtime (#​4606)

Fixes

• Cache network capabilities and status to reduce IPC calls (#​4560)
• Deduplicate battery breadcrumbs (#​4561)
• Remove unused method in ManifestMetadataReader (#​4585)
• Have single NetworkCallback registered at a time to reduce IPC calls (#​4562)
• Do not register for SystemEvents and NetworkCallbacks immediately when launched with non-foreground importance (#​4579)
• Limit ProGuard keep rules for native methods within sentry-android-ndk to the io.sentry.** namespace. (#​4427)
  • If you relied on the Sentry SDK to keep native method names for JNI compatibility within your namespace, please review your ProGuard rules and ensure the configuration still works. Especially when you're not consuming any of the default Android proguard rules (proguard-android.txt or proguard-android-optimize.txt) the following config should be present:

  -keepclasseswithmembernames class * {
    native <methods>;
  }
  

• Fix abstract method error in SentrySupportSQLiteDatabase (#​4597)
• Ensure frame metrics listeners are registered/unregistered on the main thread (#​4582)
• Do not report cached events as lost (#​4575)
  • Previously events were recorded as lost early despite being retried later through the cache
• Move and flush unfinished previous session on init (#​4624)
  • This removes the need for unnecessary blocking our background queue for 15 seconds in the case of a background app start
• Switch to compileOnly dependency for compose-ui-material (#​4630)
  • This fixes StackOverflowError when using OSS Licenses plugin

Dependencies

• Bump Native SDK from v0.8.4 to v0.10.0 (#​4623)
  • changelog
  • diff

v8.18.0

Compare Source

Features

• Add SentryUserFeedbackButton Composable (#​4559)
  • Also added Sentry.showUserFeedbackDialog static method
• Add deadlineTimeout option (#​4555)
• Add Ktor client integration (#​4527)
  • To use the integration, add a dependency on io.sentry:sentry-ktor-client, then install the SentryKtorClientPlugin on your HttpClient,
    e.g.:

    val client =
      HttpClient(Java) {
        install(io.sentry.ktorClient.SentryKtorClientPlugin) {
          captureFailedRequests = true
          failedRequestTargets = listOf(".*")
          failedRequestStatusCodes = listOf(HttpStatusCodeRange(500, 599))
        }
      }

Fixes

• Allow multiple UncaughtExceptionHandlerIntegrations to be active at the same time (#​4462)
• Prevent repeated scroll target determination during a single scroll gesture (#​4557)
  • This should reduce the number of ANRs seen in SentryGestureListener
• Do not use Sentry logging API in JUL if logs are disabled (#​4574)
  • This was causing Sentry SDK to log warnings: "Sentry Log is disabled and this 'logger' call is a no-op."
• Do not use Sentry logging API in Log4j2 if logs are disabled (#​4573)
  • This was causing Sentry SDK to log warnings: "Sentry Log is disabled and this 'logger' call is a no-op."
• SDKs send queue is no longer shutdown immediately on re-init (#​4564)
  • This means we're no longer losing events that have been enqueued right before SDK re-init.
• Reduce scope forking when using OpenTelemetry (#​4565)
  • Sentry.withScope now has the correct current scope passed to the callback. Previously our OpenTelemetry integration forked scopes an additional.
  • Overall the SDK is now forking scopes a bit less often.

v8.17.0

Compare Source

Features

• Send Timber logs through Sentry Logs (#​4490)
  • Enable the Logs feature in your SentryOptions or with the io.sentry.logs.enabled manifest option and the SDK will automatically send Timber logs to Sentry, if the TimberIntegration is enabled.
  • The SDK will automatically detect Timber and use it to send logs to Sentry.
• Send logcat through Sentry Logs (#​4487)
  • Enable the Logs feature in your SentryOptions or with the io.sentry.logs.enabled manifest option and the SDK will automatically send logcat logs to Sentry, if the Sentry Android Gradle plugin is applied.
  • To set the logcat level check the Logcat integration documentation.
• Read build tool info from sentry-debug-meta.properties and attach it to events (#​4314)

Dependencies

• Bump OpenTelemetry (#​4532)
  • opentelemetry-sdk to 1.51.0
  • opentelemetry-instrumentation to 2.17.0
  • opentelemetry-javaagent to 2.17.0
  • opentelemetry-semconv to 1.34.0
  • We are now configuring OpenTelemetry to still behave the same way it did before for span names it generates in GraphQL auto instrumentation (#​4537)
• Bump Gradle from v8.14.2 to v8.14.3 (#​4540)
  • changelog
  • diff

Fixes

• Use Spring Boot Starter 3 in sentry-spring-boot-starter-jakarta (#​4545)
  • While refactoring our dependency management, we accidentally added Spring Boot 2 and Spring Boot Starter 2 as dependencies of sentry-spring-boot-starter-jakarta, which is intended for Spring Boot 3.
  • Now, the correct dependencies (Spring Boot 3 and Spring Boot Starter 3) are being added.

v8.16.0

Compare Source

Features

• Send JUL logs to Sentry as logs (#​4518)
  • You need to enable the logs feature, either in sentry.properties:

    logs.enabled=true

  • Or, if you manually initialize Sentry, you may also enable logs on Sentry.init:

    Sentry.init(options -> {
      ...
      options.getLogs().setEnabled(true);
    });

  • It is also possible to set the minimumLevel in logging.properties, meaning any log message >= the configured level will be sent to Sentry and show up under Logs:

    io.sentry.jul.SentryHandler.minimumLevel=CONFIG

• Send Log4j2 logs to Sentry as logs (#​4517)
  • You need to enable the logs feature either in sentry.properties:

    logs.enabled=true

  • If you manually initialize Sentry, you may also enable logs on Sentry.init:

    Sentry.init(options -> {
      ...
      options.getLogs().setEnabled(true);
    });

  • It is also possible to set the minimumLevel in log4j2.xml, meaning any log message >= the configured level will be sent to Sentry and show up under Logs:

    <Sentry name="Sentry"
        dsn="your DSN"
        minimumBreadcrumbLevel="DEBUG"
        minimumEventLevel="WARN"
        minimumLevel="DEBUG"
    />

v8.15.1

Compare Source

Fixes

• Enabling Sentry Logs through Logback in Spring Boot config did not work in 3.15.0 (#​4523)

v8.15.0

Compare Source

Features

• Add chipset to device context (#​4512)

Fixes

• No longer send out empty log envelopes (#​4497)
• Session Replay: Expand fix for crash on devices to all Unisoc/Spreadtrum chipsets (#​4510)
• Log parameter objects are now turned into String via toString (#​4515)
  • One of the two SentryLogEventAttributeValue constructors did not convert the value previously.
• Logs are now flushed on shutdown (#​4503)
• User Feedback: Do not redefine system attributes for SentryUserFeedbackButton, but reference them instead (#​4519)

Features

• Send Logback logs to Sentry as logs (#​4502)
  • You need to enable the logs feature and can also set the minimumLevel for log events:

    <appender name="sentry" class="io.sentry.logback.SentryAppender">
      <options>
        <!-- NOTE: Replace the test DSN below with YOUR OWN DSN to see the events from this app in your Sentry project/dashboard -->
        <dsn>https://502f25099c204a2fbf4cb16edc5975d1@&#8203;o447951.ingest.sentry.io/5428563</dsn>
        <logs>
          <enabled>true</enabled>
        </logs>
      </options>
      <!-- Demonstrates how to modify the minimum values -->
      <!-- Default for Events is ERROR -->
      <minimumEventLevel>WARN</minimumEventLevel>
      <!-- Default for Breadcrumbs is INFO -->
      <minimumBreadcrumbLevel>DEBUG</minimumBreadcrumbLevel>
      <!-- Default for Log Events is INFO -->
      <minimumLevel>INFO</minimumLevel>
    </appender>

  • For Spring Boot you may also enable it in application.properties / application.yml:

    sentry.logs.enabled=true
    sentry.logging.minimum-level=error

  • If you manually initialize Sentry, you may also enable logs on Sentry.init:

    Sentry.init(options -> {
      ...
      options.getLogs().setEnabled(true);
    });

  • Enabling via sentry.properties is also possible:

    logs.enabled=true

• Automatically use SentryOptions.Logs.BeforeSendLogCallback Spring beans (#​4509)

Dependencies

• Bump Gradle from v8.14.1 to v8.14.2 (#​4473)
  • changelog
  • diff

v8.14.0

Compare Source

Fixes

• Fix Session Replay masking for newer versions of Jetpack Compose (1.8+) (#​4485)

Features

• Add New User Feedback Widget (#​4450)
  • This widget is a custom button that can be used to show the user feedback form
• Add New User Feedback form (#​4384)
  • We now introduce SentryUserFeedbackDialog, which extends AlertDialog, inheriting the show() and cancel() methods, among others.
    To use it, just instantiate it and call show() on the instance (Sentry must be previously initialized).
    For customization options, please check the User Feedback documentation.

    import io.sentry.android.core.SentryUserFeedbackDialog;
    
    new SentryUserFeedbackDialog.Builder(context).create().show();

    import io.sentry.android.core.SentryUserFeedbackDialog
    
    SentryUserFeedbackDialog.Builder(context).create().show()

• Add user.id, user.name and user.email to log attributes (#​4486)
• User name attribute has been deprecated, please use username instead (#​4486)
• Add device (device.brand, device.model and device.family) and OS (os.name and os.version) attributes to logs (#​4493)
• Serialize preContext and postContext in SentryStackFrame (#​4482)

Internal

• User Feedback now uses SentryUser.username instead of SentryUser.name (#​4494)

v8.13.3

Compare Source

Fixes

• Send UI Profiling app start chunk when it finishes (#​4423)
• Republish Javadoc #​4457
• Finalize OkHttpEvent even if no active span in SentryOkHttpInterceptor #​4469
• Session Replay: Do not capture current replay for cached events from the past (#​4474)
• Session Replay: Correctly capture Dialogs and non full-sized windows (#​4354)
• Session Replay: Fix inconsistent segment_id (#​4471)
• Session Replay: Fix crash on devices with the Unisoc/Spreadtrum T606 chipset (#​4477)

v8.13.2

Compare Source

Fixes

• Don't apply Spring Boot plugin in sentry-spring-boot-jakarta (#​4456)
  • The jar for io.sentry:sentry-spring-boot-jakarta is now correctly being built and published to Maven Central.

v8.13.1

Compare Source

Fixes

• Fix SentryAndroid.init crash if SDK is initialized from a background thread while an Activity is in resumed state (#​4449)

Dependencies

• Bump Gradle from v8.14 to v8.14.1 (#​4437)
  • changelog
  • diff

v8.13.0

Compare Source

Features

• Add debug mode for Session Replay masking (#​4357)
  • Use Sentry.replay().enableDebugMaskingOverlay() to overlay the screen with the Session Replay masks.
  • The masks will be invalidated at most once per frameRate (default 1 fps).
• Extend Logs API to allow passing in attributes (#​4402)
  • Sentry.logger.log now takes a SentryLogParameters
  • Use SentryLogParameters.create(SentryAttributes.of(...)) to pass attributes
    • Attribute values may be of type string, boolean, integer or double.
    • Other types will be converted to string. Currently we simply call toString() but we might offer more in the future.
    • You may manually flatten complex types into multiple separate attributes of simple types.
      • e.g. intead of SentryAttribute.named("point", Point(10, 20)) you may store it as SentryAttribute.integerAttribute("point.x", point.x) and SentryAttribute.integerAttribute("point.y", point.y)
    • SentryAttribute.named() will automatically infer the type or fall back to string.
    • SentryAttribute.booleanAttribute() takes a Boolean value
    • SentryAttribute.integerAttribute() takes a Integer value
    • SentryAttribute.doubleAttribute() takes a Double value
    • SentryAttribute.stringAttribute() takes a String value
  • We opted for handling parameters via SentryLogParameters to avoid creating tons of overloads that are ambiguous.

Fixes

• Isolation scope is now forked in OtelSentrySpanProcessor instead of OtelSentryPropagator (#​4434)
  • Since propagator may never be invoked we moved the location where isolation scope is forked.
  • Not invoking OtelSentryPropagator.extract or having a sentry-trace header that failed to parse would cause isolation scope not to be forked.
  • This in turn caused data to bleed between scopes, e.g. from one request into another

Dependencies

• Bump Spring Boot to 3.5.0 (#​4111)

v8.12.0

Compare Source

Features

• Add new User Feedback API (#​4286)
  • We now introduced Sentry.captureFeedback, which supersedes Sentry.captureUserFeedback
• Add Sentry Log Feature (#​4372)
  • The feature is disabled by default and needs to be enabled by:
    • options.getLogs().setEnabled(true) in Sentry.init / SentryAndroid.init
    • <meta-data android:name="io.sentry.logs.enabled" android:value="true" /> in AndroidManifest.xml
    • logs.enabled=true in sentry.properties
    • sentry.logs.enabled=true in application.properties
    • sentry.logs.enabled: true in application.yml
  • Logs can be captured using Sentry.logger().info() and similar methods.
  • Logs also take a format string and arguments which we then send through String.format.
  • Please use options.getLogs().setBeforeSend() to filter outgoing logs

Fixes

• Hook User Interaction integration into running Activity in case of deferred SDK init (#​4337)

Dependencies

• Bump Gradle from v8.13 to v8.14.0 (#​4360)
  • changelog
  • diff

v8.11.1

Compare Source

Fixes

• Fix Android profile chunk envelope type for UI Profiling (#​4366)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[qlty-cloud-legacy]

Code Climate has analyzed commit 54dde0c and detected 0 issues on this pull request.

View more on Code Climate.