Hi,
I am trying to build the Android apk with MABS 9, but its failing when I checked the build log in that I found this:
[2024-03-26T09:37:32.077Z] [VERBOSE] [Build] WARNING: [Processor] Library 'gradle/caches/modules-2/files-2.1/com.salesforce.marketingcloud/marketingcloudsdk/8.0.7/e17f38df2ab073bddc19fba69acdf00eac554abc/marketingcloudsdk-8.0.7.aar' contains references to both AndroidX and old support library. This seems like the library is partially migrated. Jetifier will try to rewrite the library anyway.
[2024-03-26T09:37:32.077Z] [VERBOSE] [Build] Example of androidX reference: 'androidx/annotation/RestrictTo$Scope'
[2024-03-26T09:37:32.077Z] [VERBOSE] [Build] Example of support library reference: 'android/support/annotation/Keep'
[2024-03-26T09:37:32.676Z] [VERBOSE] [Build] WARNING: [Processor] Library 'gradle/caches/modules-2/files-2.1/com.google.android.exoplayer/exoplayer-ui/2.19.1/f2854c993ee7c931a9970c22ca8a35ace6b3d9af/exoplayer-ui-2.19.1.aar' contains references to both AndroidX and old support library. This seems like the library is partially migrated. Jetifier will try to rewrite the library anyway.
Does anyone has idea how to check where this "exoplayer-ui " library is used or which plugin is using this?
Note: I cannot share the whole build log as this is not personal env, working on client env. Just want to know the path how to trace this kind of issues.
https://stackoverflow.com/questions/63592197/contains-references-to-both-androidx-and-old-support-library
Please refer above link.
Regrads,
amreen
Hi there,
The warning messages indicate that there are conflicting references to both AndroidX and the old support library within the 'marketingcloudsdk' and 'exoplayer-ui' libraries.
To trace where the 'exoplayer-ui' library is being used or which plugin is utilizing it, you can follow these steps:
Check Gradle Dependencies: Review your project's Gradle dependencies in your build.gradle files. Look for any references to 'exoplayer-ui' or similar libraries.
Inspect Code: Search your project's codebase for any direct imports or usage of the 'exoplayer-ui' library. This could be in your Java/Kotlin files or XML layout files.
Analyzing Transitive Dependencies: Since these warnings mention that the libraries are partially migrated, it's possible that they are being pulled in transitively through other dependencies. You may need to analyze your project's transitive dependencies to identify which plugin or library is bringing in 'exoplayer-ui'.
Review Plugin Configurations: If you suspect a plugin might be using 'exoplayer-ui', review the configurations of plugins you've added to your project. Check any plugin documentation or settings that might indicate its usage of 'exoplayer-ui'.
Regarding the specific issue of tracing the 'exoplayer-ui' library, it might require some manual inspection of your project's setup, dependencies, and codebase. If you're still having trouble pinpointing the source of the issue, consider reaching out to your development team or seeking further assistance from the community.
Also, if you're looking for quality mobile development services, consider checking out Mavinx. They offer expertise in mobile app development and could provide valuable assistance with resolving issues like the one you're facing.
Good luck, and I hope you resolve the issue soon!