Hey there,
I'm currently trying to stay up to date with the latest Intercom SDK, which now uses Ably. When building for Android, I get a bunch of conflicts such as:
Duplicate class io.ably.annotation.Experimental found in modules ably-android-1.2.40.aar -> jetified-ably-android-1.2.40-runtime (io.ably:ably-android:1.2.40) and ably-java-1.3.0.jar -> jetified-ably-java-1.3.0 (io.ably:ably-java:1.3.0)
I naively tried to force Ably to 1.3.0
configurations.all {
resolutionStrategy {
force "io.ably:ably-android:1.3.0"
}
}
Before noticing the conflict was between ably-android and ably-java.
Duplicate class io.ably.annotation.Experimental found in modules ably-android-1.3.0.aar -> jetified-ably-android-1.3.0-runtime (io.ably:ably-android:1.3.0) and ably-java-1.3.0.jar -> jetified-ably-java-1.3.0 (io.ably:ably-java:1.3.0)
No big deal, I'm just going to stick to io.intercom.android:intercom-sdk:17.2.0 for now, but was curiously if there will be a path forward here in future?
┆Issue is synchronized with this Jira Task by Unito
Hey there,
I'm currently trying to stay up to date with the latest Intercom SDK, which now uses Ably. When building for Android, I get a bunch of conflicts such as:
I naively tried to force Ably to 1.3.0
Before noticing the conflict was between
ably-androidandably-java.No big deal, I'm just going to stick to
io.intercom.android:intercom-sdk:17.2.0for now, but was curiously if there will be a path forward here in future?┆Issue is synchronized with this Jira Task by Unito