Skip to content

8.13.0

Compare
Choose a tag to compare
@sentry-release-bot sentry-release-bot released this 26 May 11:35

Warning

Android: Please do not use this version if you're initializing the SDK manually on a background thread, as this could lead to a crash during SDK init (issue details here). We recommend using SDK version 8.13.1 or higher instead.

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)