opentelemetry-android v1.8.1 - Crash Fix for Slow Rendering on Older Devices
OpenTelemetry Android v1.8.1 shipped on November 5, 2026. It is a small bug fix release with two changes that matter if you run the SDK in production Android apps: a crash fix in the slow rendering instrumentation and a context leak fix in Services. The version builds on OpenTelemetry Java Instrumentation 2.32.0 and the Java core 1.66.0.
The full release notes are on the GitHub release page. This is not a prerelease.
Crash in slow rendering instrumentation on Android 8 to 11
The main fix targets a NoSuchMethodError crash. The slow rendering instrumentation called Duration.toSeconds(), a method that only exists from Android 12 (API 31) onward. On Android 8 through 11 (API 26 to 30) with core library desugaring not enabled, the app crashed. That is fixed now, so devices on older API levels no longer need desugaring to use this instrumentation safely. The fix is tracked in issue 2183.
If you saw crash reports on older devices after enabling slow rendering detection, this release is the one to pick up.
Context leak and lifecycle tracking fix
The second fix touches the Services singleton. It previously retained non-application contexts, which is a leak risk on Android. It also now resets its singleton on close, so lifecycle tracking keeps working after the SDK is reinitialized. That helps apps that tear down and rebuild the OpenTelemetry SDK, for example on config changes or in tests. See pull request 2188.
Versioning notes
Several artifacts still carry the -alpha suffix. The maintainers state in the notes that alpha components will keep getting breaking changes, so pin carefully if you depend on them. The versioning policy is documented in the repo’s VERSIONING.md.
Where to get it
- Release page: opentelemetry-android v1.8.1
- Repository: open-telemetry/opentelemetry-android
- Tag:
v1.8.1