AAR libs no longer created in the output folder with Android Studio 3.0

Question

I have some lib modules in my Android project. Before updating Android Studio to the new 3.0 version and so the Gradle plugin to the 3.0.0 one, I was able to find the AAR file of my libs into the builder/output folder after building the project.

It seems that the AAR libs are no longer produced in this new version.

Is there any alternative way to get them again?

`gradle [module_name]:build` or `./gradlew [module_name]:build` in terminal — Mark, Nov 12 '17 at 00:03

score 2 · Answer 1 · answered Oct 05 '18 at 07:50

2

Update: since gradle 3.2.0, you need to use bundleReleaseAar instead of bundleRelease, as noted also in why android gradle maven publish artifact bundleRelease not found

answered Oct 05 '18 at 07:50

wilos

21
3

score 1 · Accepted Answer · answered Nov 14 '17 at 13:07

1

In my case, where I am building with Jenkins and I want to have both the apk and aar in my artifacts I could achieve this by adding :[module_name]:bundleRelease to the targets.

So if your module name is test:

:app:assembleRelease :test:bundleRelease

answered Nov 14 '17 at 13:07

Torge

2,174
1
23
33

AAR libs no longer created in the output folder with Android Studio 3.0

2 Answers2