Skip to content

Update dependency io.sentry:sentry-android to v8.16.0 #5403

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: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 30, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.sentry:sentry-android 8.11.0 -> 8.16.0 age adoption passing confidence

Release Notes

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

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

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

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

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

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.

@simple-services simple-services requested review from a team and msasikanth and removed request for a team April 30, 2025 17:34
@github-actions github-actions bot enabled auto-merge (squash) April 30, 2025 17:34
@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch 4 times, most recently from 12a5aee to 0495877 Compare May 13, 2025 21:56
@renovate renovate bot changed the title Update dependency io.sentry:sentry-android to v8.11.1 Update dependency io.sentry:sentry-android to v8.12.0 May 13, 2025
@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch 6 times, most recently from 85507f1 to 8d105ff Compare May 19, 2025 11:26
@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch 4 times, most recently from bf2a4b9 to adb5c79 Compare May 26, 2025 16:31
@renovate renovate bot changed the title Update dependency io.sentry:sentry-android to v8.12.0 Update dependency io.sentry:sentry-android to v8.13.0 May 26, 2025
@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch from adb5c79 to 4a65a35 Compare May 26, 2025 21:50
@renovate renovate bot changed the title Update dependency io.sentry:sentry-android to v8.13.0 Update dependency io.sentry:sentry-android to v8.13.1 May 26, 2025
@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch from 4a65a35 to 990a07e Compare May 27, 2025 17:49
@renovate renovate bot changed the title Update dependency io.sentry:sentry-android to v8.13.1 Update dependency io.sentry:sentry-android to v8.13.2 May 27, 2025
@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch 2 times, most recently from d08c93d to 54dde0c Compare June 3, 2025 10:58
Copy link

codeclimate bot commented Jun 3, 2025

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

View more on Code Climate.

@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch 3 times, most recently from 9a07455 to 2d167be Compare June 12, 2025 12:46
@renovate renovate bot changed the title Update dependency io.sentry:sentry-android to v8.13.2 Update dependency io.sentry:sentry-android to v8.13.3 Jun 12, 2025
@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch 6 times, most recently from fdcf601 to 34f5bbc Compare June 17, 2025 23:01
@renovate renovate bot changed the title Update dependency io.sentry:sentry-android to v8.13.3 Update dependency io.sentry:sentry-android to v8.14.0 Jun 17, 2025
@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch 4 times, most recently from b08745c to 42c2583 Compare June 25, 2025 20:24
@renovate renovate bot changed the title Update dependency io.sentry:sentry-android to v8.14.0 Update dependency io.sentry:sentry-android to v8.15.0 Jun 25, 2025
@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch 2 times, most recently from 13ef8dd to 74d9e7c Compare June 26, 2025 13:47
@renovate renovate bot changed the title Update dependency io.sentry:sentry-android to v8.15.0 Update dependency io.sentry:sentry-android to v8.15.1 Jun 26, 2025
@renovate renovate bot force-pushed the renovate/io.sentry-sentry-android-8.x branch from 74d9e7c to b7cf7ba Compare June 27, 2025 11:43
@renovate renovate bot changed the title Update dependency io.sentry:sentry-android to v8.15.1 Update dependency io.sentry:sentry-android to v8.16.0 Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

0 participants