Change apk output folder in Gradle 4.1

Question

I would like to change the APK output folder and this is what I used to do:

applicationVariants.all { variant -> variant.outputs.all { def filePath = "${rootProject.rootDir.absolutePath}/apks/${variant.name}" println("My Path: " + filePath) outputFileName = filePath } }

However, it didn't work in Gradle 4.1 (Android studio 3.0 preview). Instead of generating the folder as the path above, it generated the above path inside old debug folder like image below:

Does anyone have a solution for this? Thanks.

Did the output directory change between gradle 3 and 4? platforms/android/build/outputs/apk/android-release.apk and platforms/android/build/outputs/release/android-release.apk. This difference is breaking our builds and we're not sure if it is Gradle. — Robula
– Robula, Commented Nov 14, 2017 at 13:00

Harry Han · Accepted Answer · 2018-01-05 21:08:56Z

26

This is a workaround to keep the output path same after upgrade to gradle 4.x.

applicationVariants.all { variant -> variant.outputs.all { outputFileName = "../" + outputFileName } }

now apk is generated at platforms/android/build/outputs/apk/android-release.apk

answered Jan 5, 2018 at 21:08

Harry Han

2814 silver badges7 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Aman Jain Over a year ago

This is what I am looking for.

Alexey Ozerov Over a year ago

This stopped working after upgrading to com.android.tools.build:gradle:7.4.0. Now the builder drops this warning and ignores location change: Setting outputFileName to '../../myfilename.apk' can result in incorrect behavior. Relative paths are not supported when setting an output file name. The outputFileName API supports changing the output file's name, but not its location.

azizbekian · Accepted Answer · 2017-10-28 08:22:49Z

From migration guide:

Using the Variant API to manipulate variant outputs is broken with the new plugin. It still works for simple tasks, such as changing the APK name during build time, as shown below:

  android.applicationVariants.all { variant -> variant.outputs.all { outputFileName = "${variant.name}-${variant.versionName}.apk" } }

However, more complicated tasks that involve accessing outputFile objects no longer work. That's because variant-specific tasks are no longer created during the configuration stage. This results in the plugin not knowing all of its outputs up front, but it also means faster configuration times.

Thanks. But that means there's no way to do it, right? that sounds not really good to me.
A dirty way to do it might be to move the files with a task after they've been built.
You could set a task to move the files to another location after build completion.

Marta Rodriguez · Accepted Answer · 2018-04-09 06:06:44Z

I had a similar issue, because I needed the output apk in a known folder and not in a folder depending on the computer user name. So I have fixed like this:

applicationVariants.all { variant -> variant.outputs.all { def apk = output.outputFile; def newName = apk.name.replace(".apk", "-v" + variant.versionName + "-RELEASE.apk"); newName = newName.replace("-" + variant.buildType.name, ""); outputFileName = "./" + newName } }

With this I get the apk in: ".../outputs/apk/flavorName/buildTypeName/xxx.apk"

Hope it helps you.

This solution worked for me - looks like it should be marked as the answer
This code throw an exception as "Gradle sync failed: Could not get unknown property 'output' for ApkVariantOutputImpl_Decorated" on Gradle v4.4. output.outputFile should be changed as outputFileName.
And last code will throw "Absolute path are not supported when setting an output file name."
I have edited the answer to work with the last version of gradle.

Collectives™ on Stack Overflow

Change apk output folder in Gradle 4.1

3 Answers 3

2 Comments

4 Comments

4 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

4 Comments

4 Comments

Linked

Related