[2025.08.*] Pre-release merge #5563
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [com.android.lint](https://developer.android.com/studio/build) ([source](https://android.googlesource.com/platform/tools/base)) | `8.12.0` -> `8.12.2` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [com.android.library](https://developer.android.com/studio/build) ([source](https://android.googlesource.com/platform/tools/base)) | `8.12.0` -> `8.12.2` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [com.android.application](https://developer.android.com/studio/build) ([source](https://android.googlesource.com/platform/tools/base)) | `8.12.0` -> `8.12.2` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### 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 these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/simpledotorg/simple-android). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS44Mi43IiwidXBkYXRlZEluVmVyIjoiNDEuOTEuMSIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: sagarwal <[email protected]>
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [io.sentry:sentry-android](https://redirect.github.com/getsentry/sentry-java) | `8.11.0` -> `8.20.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>getsentry/sentry-java (io.sentry:sentry-android)</summary> ### [`v8.20.0`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8200) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.19.1...8.20.0) ##### Fixes - Do not use named capturing groups for regular expressions ([#​4652](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/4612)) - Stub for setting the callback on `Sentry.init`: ```java Sentry.init(options -> { ... options.setOnDiscard( (reason, category, number) -> { // Your logic to process discarded data }); }); ``` ### [`v8.19.1`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8191) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.19.0...8.19.1) ##### Fixes - Do not store No-Op scopes onto OpenTelemetry Context when wrapping ([#​4631](https://redirect.github.com/getsentry/sentry-java/pull/4631)) - In 8.18.0 and 8.19.0 the SDK could break when initialized too late. ### [`v8.19.0`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8190) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.18.0...8.19.0) ##### Features - Add a `isEnableSystemEventBreadcrumbsExtras` option to disable reporting system events extras for breadcrumbs ([#​4625](https://redirect.github.com/getsentry/sentry-java/pull/4625)) ##### Improvements - Session Replay: Use main thread looper to schedule replay capture ([#​4542](https://redirect.github.com/getsentry/sentry-java/pull/4542)) - Use single `LifecycleObserver` and multi-cast it to the integrations interested in lifecycle states ([#​4567](https://redirect.github.com/getsentry/sentry-java/pull/4567)) - Add `sentry.origin` attribute to logs ([#​4618](https://redirect.github.com/getsentry/sentry-java/pull/4618)) - This helps identify which integration captured a log event - Prewarm `SentryExecutorService` for better performance at runtime ([#​4606](https://redirect.github.com/getsentry/sentry-java/pull/4606)) ##### Fixes - Cache network capabilities and status to reduce IPC calls ([#​4560](https://redirect.github.com/getsentry/sentry-java/pull/4560)) - Deduplicate battery breadcrumbs ([#​4561](https://redirect.github.com/getsentry/sentry-java/pull/4561)) - Remove unused method in ManifestMetadataReader ([#​4585](https://redirect.github.com/getsentry/sentry-java/pull/4585)) - Have single `NetworkCallback` registered at a time to reduce IPC calls ([#​4562](https://redirect.github.com/getsentry/sentry-java/pull/4562)) - Do not register for SystemEvents and NetworkCallbacks immediately when launched with non-foreground importance ([#​4579](https://redirect.github.com/getsentry/sentry-java/pull/4579)) - Limit ProGuard keep rules for native methods within `sentry-android-ndk` to the `io.sentry.**` namespace. ([#​4427](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/4597)) - Ensure frame metrics listeners are registered/unregistered on the main thread ([#​4582](https://redirect.github.com/getsentry/sentry-java/pull/4582)) - Do not report cached events as lost ([#​4575](https://redirect.github.com/getsentry/sentry-java/pull/4575)) - Previously events were recorded as lost early despite being retried later through the cache - Move and flush unfinished previous session on init ([#​4624](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/4630)) - This fixes `StackOverflowError` when using OSS Licenses plugin ##### Dependencies - Bump Native SDK from v0.8.4 to v0.10.0 ([#​4623](https://redirect.github.com/getsentry/sentry-java/pull/4623)) - [changelog](https://redirect.github.com/getsentry/sentry-native/blob/master/CHANGELOG.md#0100) - [diff](https://redirect.github.com/getsentry/sentry-native/compare/0.8.4...0.10.0) ### [`v8.18.0`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8180) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.17.0...8.18.0) ##### Features - Add `SentryUserFeedbackButton` Composable ([#​4559](https://redirect.github.com/getsentry/sentry-java/pull/4559)) - Also added `Sentry.showUserFeedbackDialog` static method - Add deadlineTimeout option ([#​4555](https://redirect.github.com/getsentry/sentry-java/pull/4555)) - Add Ktor client integration ([#​4527](https://redirect.github.com/getsentry/sentry-java/pull/4527)) - To use the integration, add a dependency on `io.sentry:sentry-ktor-client`, then install the `SentryKtorClientPlugin` on your `HttpClient`, e.g.: ```kotlin 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](https://redirect.github.com/getsentry/sentry-java/pull/4462)) - Prevent repeated scroll target determination during a single scroll gesture ([#​4557](https://redirect.github.com/getsentry/sentry-java/pull/4557)) - This should reduce the number of ANRs seen in `SentryGestureListener` - Do not use Sentry logging API in JUL if logs are disabled ([#​4574](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/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`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8170) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.16.0...8.17.0) ##### Features - Send Timber logs through Sentry Logs ([#​4490](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/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](https://docs.sentry.io/platforms/android/integrations/logcat/#configure). - Read build tool info from `sentry-debug-meta.properties` and attach it to events ([#​4314](https://redirect.github.com/getsentry/sentry-java/pull/4314)) ##### Dependencies - Bump OpenTelemetry ([#​4532](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/4537)) - Bump Gradle from v8.14.2 to v8.14.3 ([#​4540](https://redirect.github.com/getsentry/sentry-java/pull/4540)) - [changelog](https://redirect.github.com/gradle/gradle/blob/master/CHANGELOG.md#v8143) - [diff](https://redirect.github.com/gradle/gradle/compare/v8.14.2...v8.14.3) ##### Fixes - Use Spring Boot Starter 3 in `sentry-spring-boot-starter-jakarta` ([#​4545](https://redirect.github.com/getsentry/sentry-java/pull/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`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8160) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.15.1...8.16.0) ##### Features - Send JUL logs to Sentry as logs ([#​4518](https://redirect.github.com/getsentry/sentry-java/pull/4518)) - You need to enable the logs feature, either in `sentry.properties`: ```properties logs.enabled=true ``` - Or, if you manually initialize Sentry, you may also enable logs on `Sentry.init`: ```java 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: ```properties io.sentry.jul.SentryHandler.minimumLevel=CONFIG ``` - Send Log4j2 logs to Sentry as logs ([#​4517](https://redirect.github.com/getsentry/sentry-java/pull/4517)) - You need to enable the logs feature either in `sentry.properties`: ```properties logs.enabled=true ``` - If you manually initialize Sentry, you may also enable logs on `Sentry.init`: ```java 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: ```xml <Sentry name="Sentry" dsn="your DSN" minimumBreadcrumbLevel="DEBUG" minimumEventLevel="WARN" minimumLevel="DEBUG" /> ``` ### [`v8.15.1`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8151) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.15.0...8.15.1) ##### Fixes - Enabling Sentry Logs through Logback in Spring Boot config did not work in 3.15.0 ([#​4523](https://redirect.github.com/getsentry/sentry-java/pull/4523)) ### [`v8.15.0`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8150) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.14.0...8.15.0) ##### Features - Add chipset to device context ([#​4512](https://redirect.github.com/getsentry/sentry-java/pull/4512)) ##### Fixes - No longer send out empty log envelopes ([#​4497](https://redirect.github.com/getsentry/sentry-java/pull/4497)) - Session Replay: Expand fix for crash on devices to all Unisoc/Spreadtrum chipsets ([#​4510](https://redirect.github.com/getsentry/sentry-java/pull/4510)) - Log parameter objects are now turned into `String` via `toString` ([#​4515](https://redirect.github.com/getsentry/sentry-java/pull/4515)) - One of the two `SentryLogEventAttributeValue` constructors did not convert the value previously. - Logs are now flushed on shutdown ([#​4503](https://redirect.github.com/getsentry/sentry-java/pull/4503)) - User Feedback: Do not redefine system attributes for `SentryUserFeedbackButton`, but reference them instead ([#​4519](https://redirect.github.com/getsentry/sentry-java/pull/4519)) ##### Features - Send Logback logs to Sentry as logs ([#​4502](https://redirect.github.com/getsentry/sentry-java/pull/4502)) - You need to enable the logs feature and can also set the `minimumLevel` for log events: ```xml <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@​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`: ```properties sentry.logs.enabled=true sentry.logging.minimum-level=error ``` - If you manually initialize Sentry, you may also enable logs on `Sentry.init`: ```java Sentry.init(options -> { ... options.getLogs().setEnabled(true); }); ``` - Enabling via `sentry.properties` is also possible: ```properties logs.enabled=true ``` - Automatically use `SentryOptions.Logs.BeforeSendLogCallback` Spring beans ([#​4509](https://redirect.github.com/getsentry/sentry-java/pull/4509)) ##### Dependencies - Bump Gradle from v8.14.1 to v8.14.2 ([#​4473](https://redirect.github.com/getsentry/sentry-java/pull/4473)) - [changelog](https://redirect.github.com/gradle/gradle/blob/master/CHANGELOG.md#v8142) - [diff](https://redirect.github.com/gradle/gradle/compare/v8.14.1...v8.14.2) ### [`v8.14.0`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8140) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.13.3...8.14.0) ##### Fixes - Fix Session Replay masking for newer versions of Jetpack Compose (1.8+) ([#​4485](https://redirect.github.com/getsentry/sentry-java/pull/4485)) ##### Features - Add New User Feedback Widget ([#​4450](https://redirect.github.com/getsentry/sentry-java/pull/4450)) - This widget is a custom button that can be used to show the user feedback form - Add New User Feedback form ([#​4384](https://redirect.github.com/getsentry/sentry-java/pull/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](https://docs.sentry.io/platforms/android/user-feedback/configuration/). ```java import io.sentry.android.core.SentryUserFeedbackDialog; new SentryUserFeedbackDialog.Builder(context).create().show(); ``` ```kotlin import io.sentry.android.core.SentryUserFeedbackDialog SentryUserFeedbackDialog.Builder(context).create().show() ``` - Add `user.id`, `user.name` and `user.email` to log attributes ([#​4486](https://redirect.github.com/getsentry/sentry-java/pull/4486)) - User `name` attribute has been deprecated, please use `username` instead ([#​4486](https://redirect.github.com/getsentry/sentry-java/pull/4486)) - Add device (`device.brand`, `device.model` and `device.family`) and OS (`os.name` and `os.version`) attributes to logs ([#​4493](https://redirect.github.com/getsentry/sentry-java/pull/4493)) - Serialize `preContext` and `postContext` in `SentryStackFrame` ([#​4482](https://redirect.github.com/getsentry/sentry-java/pull/4482)) ##### Internal - User Feedback now uses SentryUser.username instead of SentryUser.name ([#​4494](https://redirect.github.com/getsentry/sentry-java/pull/4494)) ### [`v8.13.3`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8133) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.13.2...8.13.3) ##### Fixes - Send UI Profiling app start chunk when it finishes ([#​4423](https://redirect.github.com/getsentry/sentry-java/pull/4423)) - Republish Javadoc [#​4457](https://redirect.github.com/getsentry/sentry-java/pull/4457) - Finalize `OkHttpEvent` even if no active span in `SentryOkHttpInterceptor` [#​4469](https://redirect.github.com/getsentry/sentry-java/pull/4469) - Session Replay: Do not capture current replay for cached events from the past ([#​4474](https://redirect.github.com/getsentry/sentry-java/pull/4474)) - Session Replay: Correctly capture Dialogs and non full-sized windows ([#​4354](https://redirect.github.com/getsentry/sentry-java/pull/4354)) - Session Replay: Fix inconsistent `segment_id` ([#​4471](https://redirect.github.com/getsentry/sentry-java/pull/4471)) - Session Replay: Fix crash on devices with the Unisoc/Spreadtrum T606 chipset ([#​4477](https://redirect.github.com/getsentry/sentry-java/pull/4477)) ### [`v8.13.2`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8132) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.13.1...8.13.2) ##### Fixes - Don't apply Spring Boot plugin in `sentry-spring-boot-jakarta` ([#​4456](https://redirect.github.com/getsentry/sentry-java/pull/4456)) - The jar for `io.sentry:sentry-spring-boot-jakarta` is now correctly being built and published to Maven Central. ### [`v8.13.1`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8131) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.13.0...8.13.1) ##### Fixes - Fix `SentryAndroid.init` crash if SDK is initialized from a background thread while an `Activity` is in resumed state ([#​4449](https://redirect.github.com/getsentry/sentry-java/pull/4449)) ##### Dependencies - Bump Gradle from v8.14 to v8.14.1 ([#​4437](https://redirect.github.com/getsentry/sentry-java/pull/4437)) - [changelog](https://redirect.github.com/gradle/gradle/blob/master/CHANGELOG.md#v8141) - [diff](https://redirect.github.com/gradle/gradle/compare/v8.14...v8.14.1) ### [`v8.13.0`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8130) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.12.0...8.13.0) ##### Features - Add debug mode for Session Replay masking ([#​4357](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/4111)) ### [`v8.12.0`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8120) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.11.1...8.12.0) ##### Features - Add new User Feedback API ([#​4286](https://redirect.github.com/getsentry/sentry-java/pull/4286)) - We now introduced Sentry.captureFeedback, which supersedes Sentry.captureUserFeedback - Add Sentry Log Feature ([#​4372](https://redirect.github.com/getsentry/sentry-java/pull/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](https://redirect.github.com/getsentry/sentry-java/pull/4337)) ##### Dependencies - Bump Gradle from v8.13 to v8.14.0 ([#​4360](https://redirect.github.com/getsentry/sentry-java/pull/4360)) - [changelog](https://redirect.github.com/gradle/gradle/blob/master/CHANGELOG.md#v8140) - [diff](https://redirect.github.com/gradle/gradle/compare/v8.13...v8.14.0) ### [`v8.11.1`](https://redirect.github.com/getsentry/sentry-java/blob/HEAD/CHANGELOG.md#8111) [Compare Source](https://redirect.github.com/getsentry/sentry-java/compare/8.11.0...8.11.1) ##### Fixes - Fix Android profile chunk envelope type for UI Profiling ([#​4366](https://redirect.github.com/getsentry/sentry-java/pull/4366)) </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/simpledotorg/simple-android). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNjQuMCIsInVwZGF0ZWRJblZlciI6IjQxLjgyLjciLCJ0YXJnZXRCcmFuY2giOiJtYXN0ZXIiLCJsYWJlbHMiOltdfQ==--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: sagarwal <[email protected]>
simple-services
requested review from
a team and
siddh1004
and removed request for
a team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A new release train Release is starting. The master branch has to be merged into staging branch.