Skip to content

8.65.0

Latest

Choose a tag to compare

@sentry-release-bot sentry-release-bot released this 17 Nov 15:14

Features

  • Session Replay: Add Sentry.replay().pauseTouchTracking() and resumeTouchTracking() to stop recording touches on sensitive screens, such as a custom PIN pad, while the screen recording continues. Touch tracking stays paused until resumeTouchTracking() is called, also for new replays and after resume() (#6546)

Performance

  • Most SDK log calls no longer allocate when debug is off (#6600)

Behavioral Changes

  • Nav3: Returning to an Activity or Fragment with its own SentryNavEffect within the app (e.g., closing the Activity that covered it, swiping back to its ViewPager2 page, or dismissing a dialog over it) now starts a new navigation transaction for the current destination if the previous one finished, so spans produced upon return can now be consistently captured (#6482)
  • Nav3: ui.load transactions are bound to IScope in preference to Nav3 transactions when transitioning between Activities, matching Nav2 behavior (API 29+) (#6484)

Fixes

  • Session Replay: Fix Compose masking for Jetpack Compose 1.13. If the SDK can't walk the Compose tree of a screen, it now masks the whole Compose view instead of recording it unmasked (#6626)
  • Session Replay: Send Ktor client network request start and end times in milliseconds, so the requests line up with the replay (#6619)
  • Nav3: Stop attributing errors and spans from an Activity or ViewPager2 page without a SentryNavEffect to the most recently visited Nav3 root (#6483)
  • Android: Count deep sleep in breadcrumb, screenshot and view hierarchy debounce windows, so the first low-memory or battery breadcrumb after a long Doze is no longer dropped (#6590)
  • Android: Mark transactions and spans that finish after their deadline as deadline_exceeded, so ui.load transactions with TTID, TTFD or app start values that are hours long after a device sleep no longer report ok (#6599)
  • Android: Register network callbacks on API 24–25 when AndroidConnectionStatusProvider is created with a custom Handler, instead of failing because the Handler overload needs API 26 (#6634)

Dependencies

  • Bump OpenTelemetry (#6602)
    • OpenTelemetry to 1.67.0 (was 1.63.0)
    • OpenTelemetry Instrumentation to 2.33.1 (was 2.29.0)
    • OpenTelemetry Instrumentation Alpha to 2.33.1-alpha (was 2.29.0-alpha)
    • OpenTelemetry Semantic Conventions to 1.44.0 (was 1.42.0)
    • OpenTelemetry Semantic Conventions Alpha to 1.44.0-alpha (was 1.42.0-alpha)
    • OpenTelemetry 1.67 creates no-op spans when no SpanProcessor is configured. If you construct the OpenTelemetry SDK manually while using sentry-opentelemetry-otlp classes directly, configure a span processor. Without one, Sentry cannot inspect outgoing request URLs and may inject sentry-trace and baggage headers into destinations excluded by tracePropagationTargets. Standard OTLP exporter, Sentry Java agent, and agentless setups already configure one.