You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated both Embrace and OneSignal and again OneSignal broke the build by not handling transitive OpTel dependencies and referring to some alpha version in OpTel that doesn't exist in newer versions.
com.onesignal:otel (both 5.9.7 and 5.9.8, unchanged) imports opentelemetry-bom:1.55.0 and io.opentelemetry.contrib:opentelemetry-disk-buffering:1.51.0-alpha
io.opentelemetry.kotlin:java-typealiases-android:0.6.0, which Embrace 9.1.0 pulls in, imports opentelemetry-bom:1.64.0
Gradle picks the higher → OTel SDK 1.64.0 wins
disk-buffering:1.51.0-alpha references io.opentelemetry.sdk.logs.data.internal.ExtendedLogRecordData — an internal-package class that exists in 1.51–1.55 but not 1.64 → R8
missing-class error
Claude says this can't be avoided with a don'twarn due to the code getting removed but being referred to.
Steps to reproduce?
1. Use OneSignal SDK
2. Use another SDK that has a more up to date Otel 1.64 in this instance
3. Build Fails.
What did you expect to happen?
I expected the build to work regardless of other libraries having a more up to date version of Otel.
Activity
abdulraqeeb33 commentedon Aug 12, 2026
thank you for raising the request @jt-gilkeson - we are working on this and will put out a new version with a fix shortly.
jt-gilkeson commentedon Aug 19, 2026
I take it from the release notes this didn't make it into 5.9.9?
abdulraqeeb33 commentedon Aug 20, 2026
hey @jt-gilkeson - we will mostly remove Otel in the next release. Hopefully next week. Stay tuned.
abdulraqeeb33 commentedon Sep 9, 2026
hey @jt-gilkeson, this is fixed in 5.10.0. We removed OpenTelemetry from the SDK, so the R8 clash should no longer happen. Please update to the latest version: https://github.com/OneSignal/OneSignal-Android-SDK/releases/tag/5.10.0