Skip to content

chore(deps): update Android SDK to v8.16.0 #3024

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 flutter/scripts/update-android.sh from 8.12.0 to 8.16.0.

Auto-generated by a dependency updater.

Changelog

8.16.0

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"
      />

8.15.1

Fixes

  • Enabling Sentry Logs through Logback in Spring Boot config did not work in 3.15.0 (#4523)

8.15.0

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://502f25099c204a2fbf4cb16edc5975d1o447951.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

8.14.0

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)

8.13.3

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)

8.13.2

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.

8.13.1

Fixes

  • Fix SentryAndroid.init crash if SDK is initialized from a background thread while an Activity is in resumed state (#4449)

Dependencies

8.13.0

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

  • Bump Spring Boot to 3.5.0 (#4111)

@bruno-garcia bruno-garcia force-pushed the deps/flutter/scripts/update-android.sh/8.16.0 branch from 12609ca to 8e49a32 Compare June 27, 2025 11:37
Copy link

codecov bot commented Jun 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.10%. Comparing base (707bb36) to head (0eee64d).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3024      +/-   ##
==========================================
+ Coverage   86.87%   89.10%   +2.23%     
==========================================
  Files         125       95      -30     
  Lines        4334     3138    -1196     
==========================================
- Hits         3765     2796     -969     
+ Misses        569      342     -227     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@bruno-garcia bruno-garcia force-pushed the deps/flutter/scripts/update-android.sh/8.16.0 branch from 8e49a32 to 0eee64d Compare June 27, 2025 13:11
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