Android SDK Changelog
6.14.0
October 31, 2024
- Extensive improvements to the resiliency and performance of telemetry persistence and delivery, especially under adverse device and network conditions.
- Fixed issue where feature flags were not being cached and applied consistently.
- New runtime dependency: OkHttp 4.12.
- See the FAQ here if you want to use a lower version at runtime (not recommend or supported).
6.13.0
September 12, 2024
- Improve SDK startup performance.
- Fix issue with capturing details of network requests with long URLs.
- Increase default ANR call stack depth to 200 frames.
6.12.2
September 11, 2024
- Fix race condition on app startup when native crash capture is enabled that could result in a crash when the native delegate is accessed before the library is loaded
6.12.1
September 6, 2024
- Fix JVM crash recording and Embrace API request retries when Embrace enums are obfuscated.
- Improve delivery retry of sessions ended by a native crash or background process termination.
6.12.0
September 5, 2024
This version contains a bug where obfuscating Embrace classes will lead to JVM crashes not being recorded and failed requests to Embrace not being retried after that app process terminates.
This version should not be used, but you can workaround this by adding the following keep rule to your Proguard file so R8 will bypass obfuscation for the matched code:
-keep class io.embrace.android.embracesdk.** { *; }
- Improve SDK startup performance.
- Increase resilience of telemetry delivery under poor network conditions.
- Add configuration to redact values for custom property keys on a denylist.
- Fix bug at build time that invalidated the Gradle configuration cache when the native crash capture feature was disabled.
6.11.0
August 27, 2024
- Update cached background activities when session properties are modified.
- Apply configuration defined in
embrace-config.json
properly if appId is not specified (Fix for #1219). - Restore access via synthetic properties in Kotlin for
getDeviceId()
andgetLastRunEndState()
(Fix for #1253). - Update OpenTelemetry Java SDK and BoM to 1.41.0.
6.10.0
August 13, 2024
- Support Android 15 and devices that use 16KB native page size.
- Updated minimum requirements to the following:
- JDK 11
- Android SDK Platform 34
- Gradle 7.5.1
- AGP 7.4.2
- Kotlin 1.8.22
- Improve R8 ruleset to further reduce the size of the SDK binary.
- Upload native symbols by default during the build process unless explicitly disabled.
- Split main SDK module (
io.embrace.embrace-android-sdk
) into several modules.- This is an internal change and has no direct user impact. App dependencies on Embrace remain unchanged.
Embrace.getDeviceId()
andEmbrace.getLastEndState()
only accessible as functions but not as properties in Kotlin.
6.9.2
August 1, 2024
- Fix session recording after app backgrounding if Background Activity is disabled.
Version 6.9.0 and 6.9.1 have an issue recording sessions after an app backgrounds if Background Activity is disabled.
Do not use these versions of the SDK. This issue has been addressed in 6.9.2.
6.9.1
July 10, 2024
- Fix the SDK version sent in session payloads
6.9.0
July 4, 2024
- 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 Traces 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 Traces 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.
- Provide implementation of the OpenTelemetry Tracing API.
- Enhance Traces 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.3
July 17, 2024
- No change to functionality. Remove error log integration verification explicitly for apps that don't use R8 to strip out unreferenced classes.
6.8.2
June 7, 2024
- Remove dependency on the configuration attribute
enable_automatic_activity_capture
for manually capturing views
6.8.1
June 4, 2024
- Fix a build error while reading the api_token from an environment variable.
6.8.0
May 28, 2024
- 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
April 22, 2024
- Support configuration of OpenTelemetry Exporters to export Logs data as OpenTelemetry LogRecord.
6.6.0
April 19, 2024
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
- THE OpenTelemetry Release! The Embrace Android SDK now uses the OpenTelemetry Java SDK at its core.
- This means the bulk of the telemetry is 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!
6.5.0
March 14, 2024
- Increase our minimum Gradle version to 6.5.1
- Fully support configuration cache on all Gradle versions.
- Fix issue with active Moments being lost when a new session starts.
6.4.0
March 6, 2024
- Traces improvements
- Support configuration of OpenTelemetry Exporters to export Traces 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
February 23, 2024
- 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
6.3.1
February 2, 2024
The Configuration Cache feature for Gradle 8.4+ is not compatible with this release due to an issue in Gradle tooling. Please disable this in developer builds when used with this release or use an older version of Gradle.
- Support for Gradle 8.4+
- Plus all the performance enhancements of 6.3.0!
6.3.0
January 31, 2024
Gradle 8.4+ is not supported by this version when the NDK crash capture feature is off. Please use 6.3.1 to ensure all expected Gradle versions are supported.
- A plethora of performance and reliability improvements!
- Increased speed and efficiency of data serialization and persistence
- Reduced amount of disk space used to save data not-yet delivered
- Optimized thread usage for background work
- Eliminated network requests sent when starting new sessions
- Improved handling of network retries when the backend is too busy
- Prioritized session delivery over other payloads
- Capture thermal status change events by default
- Capture CPU and GPU info by default
- Enable all tracing functionality when SDK startup is complete
6.2.0
December 13, 2023
- Removed the capture of unused beta features: strict mode violation, activity lifecycle,
- Improved the delivery of session messages with changes in the DeliveryService class
- Removed unused ANR process errors
- Gzip encode HTTP requests via stream
- Prioritize most recent api calls when limit is reached.
- Avoid dropping session when endSession called
6.1.0
November 24, 2023
- Enabled Traces by default
- Improved build performance of the Gradle plugin
- Improved session data delivery retries
- Enforce network call per session limits properly
- Fixed premature clearing of breadcrumbs on background activities
6.0.0
October 26, 2023
- Removal of deprecated methods
- Check our upgrading guide
- Increase our minSdkVersion to API 21
- Increase our minimum AGP to 4.0.0
- Increase our minimum Gradle version to 6.1.1
- Set the minimum OkHttp version to 4.0.0
We strongly recommend that Embrace customers ensure their apps meet the criteria above.
5.25.1
December 7, 2023
- Fixed a validation issue when calling deprecated method logNetworkRequest.
5.25.0
October 10, 2023
- Added support for tap tracking on Jetpack Compose elements.
- Added support for the Network Span Forwarding feature that enables the propagate of a W3C-compliant traceheader in requests to Embrace so a span can be created and forwarded to the customer servers.
- Fixed propagation of error type and message when recording incomplete network requests.
- The SDK now captures ANR data using the ApplicationExitInfo API for Android 11+.
- Fixed a rare issue when network logging was being done on a URLConnection whose Response is no longer accessible.
- Fixed a bug where calling bytes() on a gzipped OkHttp response throws an exception.
5.24.0
September 21, 2023
- Renamed several API interfaces to standardize naming between our SDKs to better reflect what each API does.
- Added new API method to get the current session ID.
- Set custom folders for native symbols to upload during build process.
- Added Dexguard support.
- Exposed beta API for Performacing Tracing.
5.23.0
August 09, 2023
- Bug fix on retryLock function. Now the ANR monitoring is Serialized to work on a single background executor.
- Fixed missing Unity ANR
- Added Plugins DSL support. Please note that embrace-swazzler plugin name changed to "io.embrace.swazzler" when declared through Plugins DSL. Legacy buildscript block declaration remains as "embrace-swazzler".
- Fixed custom breadcrumbs limit
- Fixed an issue when capturing network content for OkHttp3 in calls with gzip content.
5.22.0
July 12, 2023
- Implemented CPU and EGL device information for devices with NDK enabled.
- Fixed a bug that caused coordinates on Jetpack Compose view to be incorrectly set at 0,0.
- Fixed an issue in the network capture feature for customers using OkHttp3 where the empty request body was not being handled correctly.
5.21.0
June 27, 2023
- Added the method getLastRunEndState() to check whether the last execution crashed or was a clean exit.
- Fixed a duplicate resources error that failed the build in some scenarios.
- Fixed a build-time issue reported when using Gradle 8 and configuration cache.
5.20.0
June 16, 2023
- Fixed false positive ANR
- Improvements in AppExitInfo capture logic
- Fixed bug for network bodies using gzip compression
- Added additional logging for unwinding native crashes
- Fixed get obj folder swazzler issue, we changed our way of getting .so files
5.19.0
May 24, 2023
- Added support for Gradle 8
5.18.2
May 11, 2023
- Fixed a build time error related to
disableDependencyInjection
property.
5.18.1
May 5, 2023
- Fixed a build time error at build time for versions
5.17.1
and5.18.0
in some specific scenarios and related withcom.squareup.okhttp3:okhttp
andcom.android.volley:volley
dependencies.
5.18.0
May 4, 2023
- Core Web vitals capture from web views
- The encoding for extracted file names is enabled for builds that use Android Gradle Plugin 4.2.1 and below. This handles build issues caused by 3rd party plugins that minify classes during the build phase.
5.17.1
Apr 27, 2023
- Upgrade compileSDK to 33
- Improvements on our CPU usage and data consumption of our delivery layer
5.16.0
Apr 04, 2023
- Added the name and message of the Exception if it is used on logError or logHandledException methods.
- Deprecated the current logPushNotification method and introduced a new one that fix compatibility issues.
5.15.2
Mar 21, 2023
- Fix an error from
5.15.1
around identifying users. - Improvements in how data is collected after session ends, to avoid extending the app process duration.
5.15.1
Mar 17, 2023
- Improvements in how data is collected after session ends, to avoid extending the app process duration.
5.14.2
Mar 7, 2023
This version has a known issue with Braze. If you need to use this specific version, you can avoid the known issue with the following configuration in your app/build.gradle
file:
swazzler {
instrumentFirebaseMessaging = false
}
- Fix first activity repeated in the timeline
- Fixes a timing bug with ANR intervals where a check on monitorThreadLag was setting the start time to be in the beginning of an ANR interval.
- Ignore useNewDependencyInstaller property from the
swazzler
block. It's now used as the unique mechanism to inject dependencies, so it's safe to remove it from yourapp/build.gradle
file
5.13.0
Jan 27, 2023
- Reduced ANRs being generated by EmbraceLogger class.
- Added feature to capture network body information.
5.12.0
Jan 19, 2023
- Fixed an issue on ndk symbols.
- Fixed an ndk issue when building.
5.11.0
Jan 11, 2023
- Capture CPU number of cores
- Compress Proguard/R8 mapping files before uploading
- Added logHandledException method
5.10.0
Dec 07, 2022
- Automatically capture push notifications when the app is on foreground.
- Added the ability to manually log push notifications.
- Capture background activity
- Power save mode changes track added
5.9.4
Dec 05, 2022
- Added the ability to report the version of the Embrace React Native SDK being used.
5.9.3
Nov 20, 2022
- It fixes a Gradle issue on anyone running Gradle < 6.2
5.9.2
Nov 28, 2022
This version has a known issue with Gradle < 6.2
- Improved Embrace startup time
5.9.1
Nov 14, 2022
- Fixed an internal exception when trying to access the jailbroken status of the device.
5.9.0
Nov 03, 2022
- Improve NDK service logs to work with strict and integration mode
- Improved the EmbraceSamples.verify() method
- Added Profile Installer to support Baseline Profiles.
5.8.0
Oct 20, 2022
- Fixed message for Ironsource and Moshi known issues.
- Automate disabling dependency injection when using EDM4U.
- Automate NDK Enabling for Unity and Native projects when value is default.
- Added integration mode to identify potential issues with the SDK integration.
- Rolled back the use of DefaultLifecycleObserver
5.7.1
Oct 18, 2022
- Fixed an ANR occurring in React Native projects using a custom Javascript bundle URL.
5.7.0
Oct 03, 2022
- New mechanism to auto-install Embrace dependencies. If you prefer to use the old mechanism, the new API can be disabled by setting the
useNewDependencyInstaller
property to false.
5.6.2
Oct 03, 2022
- Fixed a lost backward compatibility with previous Unity SDK versions.
- Fixed internal exception triggered when used androidX startup library in Unity builds.
5.6.1
Sep 22, 2022
This version has a known backward compatibility issue between the Unity SDK and the Android SDK
- Removed capture_google attribute from the embrace-config.json file.
5.6.0
Sep 20, 2022
- Prevent disk i/o strict mode violations for session caching.
- Added a step to the automatic verification that validates that the SDK is receiving lifecycle events
- Increment network timeout when uploading large mapping files.
5.5.4
Aug 30, 2022
- Performance improvement: moved some disk I/O operations on startup to a worker thread.
5.5.3
Aug 25, 2022
- Fixed a logic bug in how the previous signal handler was called that prevented native tombstones from being captured by the Android OS.
- Fixed an issue that prevented the Swazzler to build on AGP versions greater or equal than 7.2.