How to generate aar in android studio?

However, instead of compiling into an APK that runs on a device, an Android library compiles into an Android Archive (AAR) file that you can use as a dependency for an Android app module. Unlike JAR files, AAR files offer the following functionality for Android apps:

A library module is useful in the following situations:

In either case, move the files you want to reuse into a library module and then add the library as a dependency for each app module.

This page explains how to create and use an Android library module. For guidance on how to publish a library, see Publish your library

To create a new library module in your project, proceed as follows:

Once the Gradle project sync completes, the library module appears in the Project pane. If you don't see the new module folder, make sure the pane is displaying the Android view.

If you have an existing app module with code you want to reuse, you can turn it into a library module as follows:

The structure of the module remains the same, but it now operates as an Android library. The build creates an AAR file instead of an APK.

When you want to build the AAR file, select the library module in the Project window and click Build > Build APK.

You can use the Project Structure dialog to add dependencies to your project. The following sections describe how to use the dialog to add dependencies.

To use your new Android library's code in another app or library module within the same project, add a project-level dependency:

Android Studio edits your module's build.gradle or build.gradle.kts file to add the dependency, in the following form:

The recommended way to share dependencies (JARs and AARs) is with a Maven repository, either hosted on a service, such as Maven Central, or with a directory structure on your local disk. For more information on using Maven repositories, see Remote repositories.

When an Android library is published to a Maven repository, metadata is included so that the dependencies of the library are included in the consuming build. This lets the library be automatically deduplicated if it is used in multiple places.

To use your Android library's code in another app module in a different project, proceed as follows:

Check your app’s build.gradle or build.gradle.kts file to confirm that a declaration similar to the following appears (depending on the build configuration you've selected):

To use your Android library's code in another app module, proceed as follows:

To import a dependency on the Gradle build running outside of Android Studio, add a path to the dependency in your app’s build.gradle or build.gradle.kts file. For example:

For more about adding Gradle dependencies, see Add build dependencies.

Resources include all files in your project’s res/ directory, such as images. All resources in a library default to public. To make all resources implicitly private, you must define at least one specific attribute as public.

To declare a public resource, add a declaration to your library’s public.xml file. If you haven't added public resources before, you need to create the public.xml file in the res/values/ directory of your library.

The following example code creates two public string resources with the names mylib_app_name and mylib_public_string:

To prevent users of your library from accessing resources intended only for internal use, use this automatic private designation mechanism by declaring one or more public resources. Alternately, you can make all resources private by adding an empty tag. This marks nothing as public and makes all resources private.

Any resources that you want to remain visible to developers using your library should be made public.

Implicitly making attributes private prevents users of your library from receiving code completion suggestions from internal library resources and lets users rename or remove private resources without breaking clients of your library. Private resources are filtered out of code completion, and the lint tool warns you when you try to reference a private resource.

When building a library, the Android Gradle plugin gets the public resource definitions and extracts them into the public.txt file, which is then packaged inside the AAR file.

As you develop your library modules and dependent apps, be aware of the following behaviors and limitations.

The file extension for an AAR file is .aar, and the Maven artifact type is aar as well. The file itself is a ZIP file. The only mandatory entry is /AndroidManifest.xml.

An AAR file can also include one or more of the following optional entries:

This article provides Information for creating AAR for an Android Library module and use It with another android Project.

I have posted an article for creating an Android Library module in an Android Project and use that with the UI app module.

Please see the article if you need to know about creating the Library module in Android Project.

An Android library is structurally the same as an Android app module. It can include everything needed to build an app, including source code, resource files, and an Android manifest. However, instead of compiling into an APK that runs on a device, an Android library compiles into an Android Archive (AAR) file that you can use as a dependency for an Android app module. AAR files offer the following functionality for Android applications:

In addition to JAR files, Android uses a binary distribution format called Android Archive(AAR). The .aar bundle is the binary distribution of an Android Library Project. An AAR is similar to a JAR file, but it can contain resources as well as compiled byte-code. AAR files can contain Android resources and a manifest file, which allows you to bundle in shared resources like layouts and drawables in addition to Java classes and methods.

Step 1: Creating AAR

If you have already created AAR  then you can skip this step and jump to generate AAR. If you haven’t created AAR then follow these steps: Navigate to File > New > New Module.

Then select “Android Library” from the options and click the next button.

Step 2: Generate AAR

Go to Gradle at the top-right pane in android studio follow the below steps. Gradle > Drop down library name > tasks > build > assemble or assemble release

AAR will be generated in build/outputs/aar/

If you have set-up your library as an Android library that is if you have done with then follow the below steps:

You can create a new Android Library using File > New Module and selecting the “Android Library” type as already shown in Method 1.

If you cannot find .aar files under build/outputs/aar/ directory then type this command in terminal:

and after hitting ENTER button you should see the “Build Successful” message on the screen.

while creating follow below steps.

File->New->New Module->Android Library and create.

To generate AAR

Go to gradle at top right pane in android studio follow below steps.

Gradle->Drop down library name -> tasks-> build-> assemble or assemble release

AAR will be generated in build/outputs/aar/

But if we want AAR to get generated in specific folder in project directory with name you want, modify your app level build.gradle like below

Now it will create folder with name "release" in project directory which will be having AAR.

Updated Answer

In Latest releases specific path is not supported.Please add below code in library's build.gradle and rebuild project.After Rebuilding "aar",change project structure from Android to Project->navigate to your library->build->outputs->aar

• Navigate to File > Project Structure > Dependencies.
• In the Declared Dependencies tab, click and select Jar Dependency in the menu.
• In the Add Jar/Aar Dependency dialog, enter the path to your AAR or JAR file, then select the configuration to which the dependency applies.