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, Nov 14 '17 at 13:00

score 25 · Answer 1 · answered Jan 05 '18 at 21:08

25

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 05 '18 at 21:08

Harry Han

271
4
7

This is what I am looking for. – Aman Jain Apr 11 '18 at 06:17
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. – Alexey Ozerov Jan 19 '23 at 02:51

score 22 · Answer 2 · answered Oct 28 '17 at 08:22

22

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.

answered Oct 28 '17 at 08:22

azizbekian

60,783
13
169
249

Thanks. But that means there's no way to do it, right? that sounds not really good to me. – Kingfisher Phuoc Oct 28 '17 at 17:00
None that I am aware of, sorry. – azizbekian Oct 28 '17 at 18:13
1

A dirty way to do it might be to move the files with a task after they've been built. – Keab42 Nov 02 '17 at 14:46
You could set a task to move the files to another location after build completion. – Abraham Toledo Nov 16 '17 at 11:17

Marta Rodriguez · Answer 3 · 2018-04-09T06:06:44.380

13

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.

edited Apr 09 '18 at 06:06

answered Nov 07 '17 at 10:06

Marta Rodriguez

1,944
2
16
30

This solution worked for me - looks like it should be marked as the answer – Gene Bo Dec 25 '17 at 00:28
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`. – wonsuc Apr 07 '18 at 22:40
And last code will throw "Absolute path are not supported when setting an output file name." – wonsuc Apr 07 '18 at 22:42
I have edited the answer to work with the last version of gradle. – Marta Rodriguez Apr 09 '18 at 06:07

Change apk output folder in Gradle 4.1

3 Answers3

Linked