Skip to content

chore(deps): update Java SDK to v8.19.1 #446

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

Bumps scripts/update-java.sh from 8.17.0 to 8.19.1.

Auto-generated by a dependency updater.

Changelog

8.19.1

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.

8.19.0

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

8.18.0

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.

@bruno-garcia bruno-garcia force-pushed the deps/scripts/update-java.sh/8.19.1 branch from 570b61d to cb35ce3 Compare August 13, 2025 03:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant