


The experience SDKs, specifically assurance and core, reference classes from the old Android support libraries and should use their AndroidX equivalent libraries instead.
Apps that use AndroidX rely on the Jetifier to transform Adobe's SDKs in order to consume them, and are unable to drop the build time expensive 'Jetifier' due to Adobe's SDKs.
Is there any plan to update the SDKs to use AndroidX and release a newer version of the libraries with it?
Topics help categorize Community content and increase your ability to discover relevant content.
Hi @baksansk, we have added it to our backlog, but no ETA yet.
Views
Replies
Sign in to like this content
Total Likes
@Yansong Any ETA on this yet? When my app now targets Android SDK 33, we get tons of build warnings about Jetifier and the ONLY thing in our app keeping us from disabling are the Adobe SDKs.
We have this nice little note in our gradle.properties now... If we set enableJetifier=false, then our build explodes with that Duplicate class issue as noted. When we backtracked the dependency chain, the issue originated in Adobe SDKs.
#
# Adobe SDKs are forcing this. Other than Adobe, we could remove this.
# Duplicate class android.support.v4.app.INotificationSideChannel found in modules core-1.8.0-runtime (androidx.core:core:1.8.0) and support-compat-27.1.1-runtime (com.android.support:support-compat:27.1.1)
#
android.enableJetifier=true
Views
Replies
Sign in to like this content
Total Likes