Releases: getsentry/sentry-java
Releases · getsentry/sentry-java
8.22.0
Features
- Move SentryLogs out of experimental (#4710)
- Add support for w3c traceparent header (#4671)
- This feature is disabled by default. If enabled, outgoing requests will include the w3c
traceparentheader. - See https://develop.sentry.dev/sdk/telemetry/traces/distributed-tracing/#w3c-trace-context-header for more details.
Sentry(Android).init(context) { options -> // ... options.isPropagateTraceparent = true }
- This feature is disabled by default. If enabled, outgoing requests will include the w3c
- Sentry now supports Spring Boot 4 M3 pre-release (#4739)
Improvements
- Remove internal API status from get/setDistinctId (#4708)
- Remove ApiStatus.Experimental annotation from check-in API (#4721)
Fixes
- Session Replay: Fix
NoSuchElementExceptioninBufferCaptureStrategy(#4717) - Session Replay: Fix continue recording in Session mode after Buffer is triggered (#4719)
Dependencies
8.21.1
8.21.0
Fixes
- Only set log template for logging integrations if formatted message differs from template (#4682)
Features
- Add support for Spring Boot 4 and Spring 7 (#4601)
- NOTE: Our
sentry-opentelemetry-agentless-springis not working yet for Spring Boot 4. Please usesentry-opentelemetry-agentuntil OpenTelemetry has support for Spring Boot 4.
- NOTE: Our
- Replace
UUIDGeneratorimplementation with Apache licensed code (#4662) - Replace
Randomimplementation with MIT licensed code (#4664) - Add support for
varsattribute inSentryStackFrame(#4686)- Breaking change: The type of the
varsattribute has been changed fromMap<String, String>toMap<String, Object>.
- Breaking change: The type of the
8.20.0
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 }); });
- Stub for setting the callback on
8.19.1
8.19.0
Warning
Android: This release is incompatible with API levels below 26. We recommend using SDK version 8.20.0 or higher instead.
Features
- Add a
isEnableSystemEventBreadcrumbsExtrasoption to disable reporting system events extras for breadcrumbs (#4625)
Improvements
- Session Replay: Use main thread looper to schedule replay capture (#4542)
- Use single
LifecycleObserverand multi-cast it to the integrations interested in lifecycle states (#4567) - Add
sentry.originattribute to logs (#4618)- This helps identify which integration captured a log event
- Prewarm
SentryExecutorServicefor 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
NetworkCallbackregistered 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-ndkto theio.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.txtorproguard-android-optimize.txt) the following config should be present:
-keepclasseswithmembernames class * { native <methods>; } - 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 (
- 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
StackOverflowErrorwhen using OSS Licenses plugin
- This fixes
Dependencies
8.18.0
Features
- Add
SentryUserFeedbackButtonComposable (#4559)- Also added
Sentry.showUserFeedbackDialogstatic method
- Also added
- Add deadlineTimeout option (#4555)
- Add Ktor client integration (#4527)
- To use the integration, add a dependency on
io.sentry:sentry-ktor-client, then install theSentryKtorClientPluginon yourHttpClient,
e.g.:val client = HttpClient(Java) { install(io.sentry.ktorClient.SentryKtorClientPlugin) { captureFailedRequests = true failedRequestTargets = listOf(".*") failedRequestStatusCodes = listOf(HttpStatusCodeRange(500, 599)) } }
- To use the integration, add a dependency on
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
- This should reduce the number of ANRs seen in
- 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.withScopenow 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.
7.22.6
Fixes
- Compress Screenshots on a background thread (#4295)
- Improve low memory breadcrumb capturing (#4325)
- Make
SystemEventsBreadcrumbsIntegrationfaster (#4330) - Fix unregister
SystemEventsBroadcastReceiverwhen entering background (#4338)- This should reduce ANRs seen with this class in the stack trace for Android 14 and above
- Pre-load modules on a background thread upon SDK init (#4348)
- Session Replay: Fix inconsistent
segment_id(#4471) - Session Replay: Do not capture current replay for cached events from the past (#4474)
- Session Replay: Fix crash on devices with the Unisoc/Spreadtrum T606 chipset (#4477)
- Session Replay: Fix masking of non-styled
TextComposables (#4361) - Session Replay: Fix masking read-only
TextFieldComposables (#4362) - Fix Session Replay masking for newer versions of Jetpack Compose (1.8+) (#4485)
- Session Replay: Expand fix for crash on devices to all Unisoc/Spreadtrum chipsets (#4510)
8.17.0 (Stable)
Features
- Send Timber logs through Sentry Logs (#4490)
- Enable the Logs feature in your
SentryOptionsor with theio.sentry.logs.enabledmanifest 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.
- Enable the Logs feature in your
- Send logcat through Sentry Logs (#4487)
- Enable the Logs feature in your
SentryOptionsor with theio.sentry.logs.enabledmanifest 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.
- Enable the Logs feature in your
- Read build tool info from
sentry-debug-meta.propertiesand attach it to events (#4314)
Dependencies
- Bump OpenTelemetry (#4532)
opentelemetry-sdkto1.51.0opentelemetry-instrumentationto2.17.0opentelemetry-javaagentto2.17.0opentelemetry-semconvto1.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)
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.
- While refactoring our dependency management, we accidentally added Spring Boot 2 and Spring Boot Starter 2 as dependencies of
8.16.1-alpha.2
Fixes
- Optimize scope when maxBreadcrumb is 0 (#4504)
- Fix javadoc on TransportResult (#4528)
- Session Replay: Fix
IllegalArgumentExceptionwhenBitmapis initialized with non-positive values (#4536) - Set thread information on transaction from OpenTelemetry attributes (#4478)
Internal
- Flattened PerformanceCollectionData (#4505)