6.9.1

• Fix the SDK version sent in session payloads

6.9.0

• OpenTelemetry compatibility improvements:
  • Provide implementation of the OpenTelemetry Tracing API.
    • Spans recorded through this API and implementation are equivalent to those recorded using the Embrace Performance Tracing API.
    • This can be obtained through the getOpenTelemetry() method, which will return working implementations for methods involving tracing. Methods involving Logs and Metrics are no-ops at the current time.
  • Stopping spans through the Embrace Performance Tracing API no longer implicitly sets Status to OK.
  • Add telemetry.distro.* resource attributes to exported signals.
  • Update OpenTelemetry SDK dependency to version 1.38 of the OpenTelemetry BOM.
  • Consume semantic conventions from OTel Semantic Conventions for Java.
• Enhance Performance Tracing API to support behavior exposed via the OpenTelemetry Tracing API.
• Change internal endpoint to which session data is sent (no user-facing behavior changes).
• Issue build warning for apps that have minSdk < 24 and are using AGP < 8.3.
  • If minSdk is lower than 24 (i.e. Android 5 and/or 6 is supported by the app), AGP version 8.3+ must be used so the app can be desugared with the proper setting.
  • See this question in the FAQ for details.
• Fix DexGuard support.

6.8.1

• Fix reading of api_token from from an environment variable instead of the config file during the build

6.8.2

• Remove dependency on the configuration attribute enable_automatic_activity_capture for manually capturing views

6.8.0

• Complete migration to OpenTelemetry, which means all app data recorded by the SDK can be sent directly to OpenTelemetry Collectors from the app.
• Allow the SDK to be used without being an Embrace customer, so data is only sent to OpenTelemetry Collectors and not to Embrace.
• Verify as part of the build that desugaring is enabled for apps supporting Android versions less than 7.0 (i.e. minSdkVerion < 24).
• Fix the location we look for flavor-specific Embrace configuration files during the build.
• Remove excessive SDK logging.

6.7.0

Support configuration of OpenTelemetry Exporters to export Logs data as OpenTelemetry LogRecord.

6.6.0

THE OpenTelemetry Release!

• We migrated the internals of the Embrace Android SDK to use the OpenTelemetry Java SDK at its core.
• This means the bulk of the telemetry are recorded as OTel signals, so they can be sent directly to OTel Collectors from the app using any Java OTLP Exporter that is compatible with Android.
• Telemetry types modeled by Embrace like sessions, crashes, ANRs, and logs have canonical representations as OTel signals using a combination of OTel and in-house semantic conventions
• The number of Embrace conventions will hopefully shrink going forward as the community comes together around a set of shared semantic conventions to standardize the world of mobile telemetry.
• We will build upon this new foundation in the coming releases to bring together the worlds of OpenTelemetry, mobile client performance observability, and RUM!
• As a result of this upgrade, API Desugaring is now a requirement for apps that support Android 5 and 6. This is a simple, well-supported process done by Android build tooling that backports certain Java 8 language features onto older Android versions that didn't have support. For more information, please see Google's documentation here

6.5.0

• Fully support configuration cache on all Gradle versions.
• Fix issue with active Moments being lost when a new session starts.

6.4.0

• Performance Tracing improvements
  • Support configuration of OpenTelemetry Exporters to export Performance Tracing data as OpenTelemetry Spans (beta).
  • Change timestamps parameters of the APIs to use milliseconds to better align with Android developer expectations.
    • Note: timestamps that are in nanoseconds will be detected and converted for now so existing instrumentation will still work, but this will be removed in an upcoming release.
  • Increase per-session limit of spans to 500 in total.
  • New methods added:
    • "getSpan" that returns a reference to an active or recently ended EmbraceSpan.
    • "startSpan" that creates and starts a span directly.
  • New functionality for existing methods:
    • Allow custom timestamps to be specified when starting and stopping a span.
    • Support adding attributes and span events to "recordSpan".
• Increase transparency of SDK startup by adding custom sections to traces recorded using Android system tracing libraries like androidx.tracing.
  • Note: only run Android system tracing on release builds running on real devices. Debug builds and emulators will not yield accurate data.
• Optimize React Native JavaScript bundleId retrieval to better support CodePush (React Native only)
• Allow configuration cache to be enabled for Gradle 8.3+
  • Note: for Gradle 8.3+, running Embrace Gradle plugin will invalidate the configuration cache

6.3.2

• Improved performance and stability of NDK serialization while the app is under memory pressure
• Added back support of OkHttp 3.13.0+, which was initially removed in this major version