The aar file doesn’t contain the nested (or transitive) dependencies and doesn’t have a pom file which describes the dependencies used by the library. It means that, if you are importing a aar file using a flatDir repo you have to specify the dependencies also in your project. In your case adding transitive=true doesn’t resolve … Read more
I was getting the same errors. This was the only thing that helped me: dependencies { compile(name:’nameOfYourAARFileWithoutExtension’, ext:’aar’) } repositories{ flatDir{ dirs ‘libs’ } } Reference: Adding local .aar files to Gradle build using “flatDirs” is not working
Supposing you have mylib.aar in your current directory, try the following: $ unzip myLib.aar -d tempFolder # or other extracting tool # Change whatever you need $ jar cvf myNewLib.aar -C tempFolder/ .
While I haven’t tried uploading the artifacts with a deployment to Sonatype (or even a local repo), here’s what I managed to come up with a few weeks ago when trying to tackle the same problem. android.libraryVariants.all { variant -> def name = variant.buildType.name if (name.equals(com.android.builder.core.BuilderConstants.DEBUG)) { return; // Skip debug builds. } def task … Read more
You put your flatDir block in the wrong repostories block. The repositories block inside buildscript tells Gradle where to find the Android-Gradle plugin, but not the rest of the dependencies. You need to have another top-level repositories block like this: repositories { mavenCentral() flatDir { dirs ‘aars’ } } I tested this and it works … Read more
According to Xavier Durochet’s explanation on G+, it’s due to one of the libraries you use having it’s own ic_launcher.png — which they of course should not (more on that at the bottom). Chances are the two icons mentioned in the log are different: one is yours and another one is most likely the generic … Read more
The AAR file consists of a JAR file and some resource files (it is basically a standard zip file with a custom file extension). Here are the steps to convert: Extract the AAR file using standard zip extract (rename it to *.zip to make it easier) Find the classes.jar file in the extracted files Rename … Read more
I have solved my problem by setting transitive attribute for my aar dependency: compile (‘com.somepackage:LIBRARY_NAME:1.0.0@aar’){ transitive=true }
I recently encountered the same issue, the fix was to remove the library from libs/ and import it using File -> New -> New Module -> Import .JAR/.AAR Package, then referencing it in the library module build.gradle file: dependencies { implementation project(“:imported_aar_module”) } If you are on a newer Android Studio version (4.0.0+), this option … Read more
AAR files are more similar to Jars than to Dlls for the following reason: Dlls can be shared across applications where as AARs and jars are packaged in with your app. AARs vs Jars: The main difference between a Jar and a AAR is that AARs include resources such as layouts, drawables etc. This makes … Read more