Cause: buildOutput.apkData must not be null

Question

My android application using Kotlin is throwing this exception when I try to Run 'app' in the emulator o in my cellphone. When I build my project it runs well, with no errors.

I am using:

SDK 28 (Android 9.0 (Pie))
Gradle 5.1.1
Gradle Plugin 3.5.0-alpha03
Kotlin 1.3.10
Java 1.8.0_151
OSX 10.13.2

    org.gradle.internal.exceptions.LocationAwareException: buildOutput.apkData must not be null
        at org.gradle.initialization.exception.DefaultExceptionAnalyser.transform(DefaultExceptionAnalyser.java:99)
        at org.gradle.initialization.exception.DefaultExceptionAnalyser.collectFailures(DefaultExceptionAnalyser.java:65)
        at org.gradle.initialization.exception.MultipleBuildFailuresExceptionAnalyser.transform(MultipleBuildFailuresExceptionAnalyser.java:39)
        at org.gradle.initialization.exception.StackTraceSanitizingExceptionAnalyser.transform(StackTraceSanitizingExceptionAnalyser.java:29)
        at org.gradle.initialization.DefaultGradleLauncher.finishBuild(DefaultGradleLauncher.java:194)
        at org.gradle.initialization.DefaultGradleLauncher.finishBuild(DefaultGradleLauncher.java:141)
        ...
    Caused by: java.lang.IllegalStateException: buildOutput.apkData must not be null
        at com.android.build.gradle.internal.ide.EarlySyncBuildOutput$Companion$load$2.invoke(EarlySyncBuildOutput.kt:103)
        at com.android.build.gradle.internal.ide.EarlySyncBuildOutput$Companion$load$2.invoke(EarlySyncBuildOutput.kt:67)
        at kotlin.sequences.TransformingSequence$iterator$1.next(Sequences.kt:174)
        at kotlin.sequences.SequencesKt___SequencesKt.toCollection(_Sequences.kt:691)
        at kotlin.sequences.SequencesKt___SequencesKt.toMutableList(_Sequences.kt:721)
        at kotlin.sequences.SequencesKt___SequencesKt.toList(_Sequences.kt:712)
        ...

I created a ticket https://issuetracker.google.com/issues/129994596 — Eugen Martynov, Apr 05 '19 at 11:35
Check Lemberg answer that works for me, I've faced that issue today — Nicky, Apr 23 '19 at 09:06
Same for Java (not necessary Kotlin) after installing Android Studio 3.5. — Patapoom, Aug 28 '19 at 12:32

score 327 · Answer 1 · edited Apr 23 '19 at 12:33

327

Click Build -> Clean Project

Then Build -> Make Project

Tested on gradle 3.5.0-alpha3, -alpha5 and 3.4.0 (project gradle)

classpath 'com.android.tools.build:gradle:3.5.0-alpha03'

edited Apr 23 '19 at 12:33

hb0

3,350
3
30
48

answered Feb 04 '19 at 16:49

Martin Pfeffer

12,471
9
59
68

1

I can confirm this is working as well with the version `com.android.tools.build:gradle:3.5.0-alpha05` (with `Build` -> `Rebuild Project` in AS) – kikoso Feb 25 '19 at 09:05
Also works for `classpath 'com.android.tools.build:gradle:3.4.0-rc02'` – luckyhandler Mar 26 '19 at 12:47
1

Sadly it requires upgrading to Android Studio 3.5, I can't tell my team to switch to an unstable channel for Android Studio updates. – void.pointer Apr 19 '19 at 15:08
@void.pointer why not? I'm on canary (also for production) for years. Can't complain about stability or bad performance (using macOS).. – Martin Pfeffer Apr 22 '19 at 17:44
8

Works on Android Studio 3.4 – Rafael Apr 23 '19 at 04:20
6

trying on AndroidStudio3.5 on Mac OS, all sdk updated, using gradle version `com.android.tools.build:gradle:3.5.0`, this solution is not working for me – Mihodi Lushan Aug 22 '19 at 08:32
@MihodiHasanLushan Delete the `build` folder and build project again. Otherwise check if your gradle is correct (sdk, dependencies, etc). Are you sure you are getting the same error message? – Martin Pfeffer Aug 22 '19 at 09:35
1

tried those, yes, I am getting this error. @MartinPfeffer – Mihodi Lushan Aug 22 '19 at 09:39
@MihodiHasanLushan for me it works only after i'ved run 'gradlew clean build' on android studio's terminal. i am using `classpath 'com.android.tools.build:gradle:3.5.0'` with android studio 3.5 on windows10 – ghita Aug 22 '19 at 11:47
Works on Android Studio 3.5. – Patapoom Aug 28 '19 at 12:32
I only had to clean since my gradle version was 3.5.1 when I updated my project fro my repo. – Juan José Melero Gómez Oct 23 '19 at 20:08
Also works for `classpath 'com.android.tools.build:gradle:3.5.3'` Android Studio 3.6.3 – Wilmer May 22 '20 at 01:49

Shubham Jain · Answer 2 · 2021-02-22T02:19:19.120

164

FOR Android Studio 3.5 | 3.6

debug builds finish without any error. Creating a signed .apk leads to the same error

buildOutput.apkData must not be null

the Simple solution that I found is. During the signing of the apk after entering the signing credentials when you navigate to the next screen then it will ask for the destination folder just change the default path.

Let's assume the current destination path is

c:\user\folder\project\app

change it to

c:\user\folder\project\

then it will generate the signed apk successfully.

edited Feb 22 '21 at 02:19

answered Aug 28 '19 at 19:24

Shubham Jain

2,365
2
17
29

6

I really appreciate your solution. Thanks. This is just simple and just really stupid build error of Android Studio. – james Aug 30 '19 at 11:53
2

Wow, you saved my life with this. However is this a bug in Android Studio or is my project messed up? – Vijay Kumar Kanta Sep 03 '19 at 13:38
@ Vijay Kumar Kanta this is an issue with the studio I hope in the new update it will be fixed – Shubham Jain Sep 03 '19 at 14:41
1

OMG, this Android Studio upgrade to 3.5 brings a lot of issues for me. – Henrique Monte Sep 05 '19 at 01:35
1

Very useful in Android 3.5.2 – CodeFluid Nov 10 '19 at 21:16
1

Thanks & Nice solution. I updated Android Studio even this error occurs in Android Studio 3.6. This solution saved my day. Thanks again – Divakar Murugesh Feb 27 '20 at 10:21
1

thanks for the solution my app has hundred to thousand c++ class so cleaning will consume time. – Pipin Indrawan Apr 30 '21 at 06:38

VIISHRUT MAVANII · Answer 3 · 2021-11-19T09:28:40.563

162

For Android Studio 3.5 & 3.6 Update (APK signed issue)

Step 1: I have resolved this issue by modifying the Destination Folder location.

Before

c:\user\folder\project\app

After

c:\user\folder\project\apk

For Android Studio 3.4 Update.

Step 1: After update Android Studio 3.4 you need to add all the dependency that used in your module or library in your app-level build.gradle.

Step 2: Clean Project(Build > Clean Project)

Step 3: Rebuild Project(Build > Rebuild Project)

Now, Your Project will compile Perfectly.

edited Nov 19 '21 at 09:28

answered May 03 '19 at 10:40

VIISHRUT MAVANII

11,410
7
34
49

1

what's that? what should I do exactly? > Step 1: After update Android Studio 3.4 you need to add all the dependency that used in your module or library in your app-level build.gradle. – babay Aug 02 '19 at 17:08
1

@babay Suppose you are using any library that is using Glide library. Then you have to add your Glide dependency in your App level build.gradle also. – VIISHRUT MAVANII Aug 02 '19 at 19:11
i got this error after step 3. APT: error: resource android:attr/fontStyle not found. – james Aug 30 '19 at 11:24
@james I think there is a resource missing. follow the below steps to find an issue. Click on Gradle(You will find in Top-Right Corner) > app_name(root) > other > assembleDebug – VIISHRUT MAVANII Aug 30 '19 at 11:49
1

@VishrutMavani Thank for your answer, but i found the really stupid error of Android studio. I just changed the build output path. That is. Solution by Shuham Jain. See below his solution. – james Aug 30 '19 at 11:55
1

'Destination Folder' is a field in Generate Signed Bundle or APK modal; – buncis Sep 12 '19 at 11:59
6

This fixed my issue in Android Studio v3.5 and a Java project. This is a pretty standard occurrence whenever building Android apps now ... (1) get a weird incomprehensible build error (2) google it (3) stack overflow (4) apply seemingly unrelated workaround in a specific order (5) pray (6) it works (7) go to step (1) – dodgy_coder Sep 27 '19 at 02:32
3

I can't believe the working solution to this problem is actually "Change the destination folder." But it is! ¯\\_(ツ)_/¯ – mkasberg Nov 24 '19 at 03:59
i do not know where is suppossed to change that directory. I have not figured out yet – Billyjoker Dec 02 '19 at 15:59
@Billyjoker During the signing APK after Entering the signing credentials when you navigate to the next screen then it will ask for the destination folder. just change the default path. – VIISHRUT MAVANII Dec 03 '19 at 03:55
Within 3.5.3, 'Change the destination folder' not supporting due to studio already disabled the change option of destination – Nuwan Withanage Jan 12 '20 at 17:13
@NuwanWithanage I have another solution & it may help you. try to generate debug signed build first then generate release signed. – VIISHRUT MAVANII Jan 15 '20 at 04:10

score 53 · Answer 4 · answered Apr 30 '19 at 18:06

53

I was getting this error also, when trying to "Generate Signed APK" for my release version. I tried all of the above methods, unfortunately none worked for me.

What worked, was generating first the debug signed version of the app, and then generating again the release one.

I do not know what exactly changed or what the original problem was, but it worked. I hope it will help you too, because this error is quite annoying...

answered Apr 30 '19 at 18:06

Kuruchy

1,330
1
14
26

1

In my case I need to generate first product flavor apk (debug to release) to last flavor (debug to release). – 林果皞 May 03 '19 at 10:45
4

Yes!! It worked for me too. thanks. I don't know why but it looks like a bug. – Doongsil May 29 '19 at 05:45
3

trying on AndroidStudio3.5 on Mac OS, all sdk updated, using gradle version `com.android.tools.build:gradle:3.5.0`, this solution is not working for me – Mihodi Lushan Aug 22 '19 at 08:32
1

In my case: AndroidStudio3.5, Build bundle(s)/apk(s) => Build apk(s), then Generate Signed APK – solo Aug 23 '19 at 02:40
1

It is crazy, but this solution works - I don't understand why. Android Studio 3.5, Windows – cVoronin Aug 30 '19 at 08:25
Its a bug in Android Studio 3..5 – Apparao Mulpuri Aug 30 '19 at 09:59

Roman Nazarevych · Answer 5 · 2019-04-29T20:31:21.667

23

Cleaning the project didn't help me but manually deleting all the auto-generated build folders in all modules helped.

edited Apr 29 '19 at 20:31

answered Apr 18 '19 at 16:11

Roman Nazarevych

7,513
4
62
67

This is the equivalent of cleaning the project. – devgianlu Apr 22 '19 at 12:56
4

No, it isn't, try to clean project from Android Studio and then check App directory for `build` directories in any file explorer, you will see that some files are still left there. – Roman Nazarevych Apr 22 '19 at 15:02
In my case I had multiple flavours, it worked once I had deleted all the build folder along with Flavour specific folders. After deleting folders, I had to close the project and reopen to get it working – Hari Jun 25 '19 at 20:17
trying on AndroidStudio3.5 on Mac OS, all sdk updated, using gradle version `com.android.tools.build:gradle:3.5.0`, this solution is not working for me – Mihodi Lushan Aug 22 '19 at 08:32

Jorgesys · Answer 6 · 2019-07-27T16:58:10.800

18

Updating to Android Studio 3.4.?, i get the message

Cause: buildOutput.apkData must not be null

looking for an answer i found the procedure:

Build -> Clean Project

but it doesn´t worked, i know that this procedure will delete the content into the /build directory but for my experience it doesn´t work in all cases, so i tried the "raw" way, deleting the directory:

/app/build/

then i rebuild the project and it worked.

edited Jul 27 '19 at 16:58

answered Jun 18 '19 at 21:30

Jorgesys

124,308
23
334
268

2

This worked for me, but I had to also remove all `/` directories (it's about `output.json` files in them). `Clean project` alone didn't solve the issue. – javaxian Aug 29 '19 at 09:53

score 9 · Answer 7 · answered Aug 28 '19 at 00:39

All the solutions didn't work with me

Android Studio V 3.5

Android gradle plugin V 3.4.2

Gradle Version V 5.1.1

Clean the project
Restart Android Studio + Invalidate Caches
Delete the build, debug, and releases folder
Make project
Generate signed APK

Reference

score 9 · Answer 8 · edited Jun 20 '20 at 09:12

9

I tried above multiple solutions but nothing has happened then I found this this and worked for me

    deleting debug/output.json and release/output.json solved my problem

Now I am able to generate apk

edited Jun 20 '20 at 09:12

Community

1
1

answered Oct 08 '19 at 13:06

Rohan Pawar

1,875
22
40

score 7 · Answer 9 · answered Aug 22 '19 at 09:34

I've tried many things to solve the issue, but nothing helped. I get this error when trying to generate a signed apk.

Downgrading to older versions of Android Studio helped (3.4.2) worked, however this is not the solution.

The 'Clean Project' function in AS does not clean the place where your generated apk is created and there is one file that may be blocking the whole procedure: output.json

Try removing output.json from .../app/projectname/release/output.json

score 5 · Answer 10 · answered May 28 '19 at 16:01

5

I was using Android Studio 3.5 beta 2 and I was having the exact same error but only on my release build. After trying every other solution I found, the only way I was able to compile again was to go back to Android Studio 3.4.

answered May 28 '19 at 16:01

amp

11,754
18
77
133

This "solution" also worked for me. Downgrade to AS 3.4.2, downloadhere: https://developer.android.com/studio/archive and changing from 3.5.0 to: classpath 'com.android.tools.build:gradle:3.4.2' – Loadeed Aug 22 '19 at 20:41

score 4 · Answer 11 · answered May 07 '19 at 11:38

4

It works for me:

delete build folder from your project manually.
in terminal of android studio type this command

if windows user

gradlew clean build

if linux user

./gradlew clean build

answered May 07 '19 at 11:38

Abhishek Garg

3,092
26
30

1

trying on AndroidStudio3.5 on Mac OS, all sdk updated, using gradle version `com.android.tools.build:gradle:3.5.0`, this solution is not working for me – Mihodi Lushan Aug 22 '19 at 08:33

score 4 · Answer 12 · answered Aug 21 '19 at 15:42

4

This issue is happens usually when you are running multiple android studio window with different projects.

The solution is

choose project than delete .gradle and build folders
than clean and rebuild the project.

please ref screen shot attached

answered Aug 21 '19 at 15:42

Suresh Maidaragi

2,173
18
25

trying on AndroidStudio3.5 on Mac OS, all sdk updated, using gradle version `com.android.tools.build:gradle:3.5.0`, this solution is not working for me – Mihodi Lushan Aug 22 '19 at 08:33
Can you try File > Invalidate caches/Restart after delete auto-generated files .gradle and build @MihodiHasanLushan – Suresh Maidaragi Aug 22 '19 at 09:06

score 4 · Answer 13 · answered Oct 13 '19 at 20:08

4

Just change the Apk release/debug location.

EX:

/home/sanaebadi/Desktop

after change :

/home/sanaebadi/apk

answered Oct 13 '19 at 20:08

Sana Ebadi

6,656
2
44
44

justnoone · Answer 14 · 2019-09-26T03:20:44.157

3

the only solution that works for me is using in my root gradle

classpath 'com.android.tools.build:gradle:3.3.0'

what i've tried : - clear all build folder manually - invalidate cache but none of these is work

PS: i'm using android studio 3.5 btw

Update :

just like @Vishrut Mavani, changing the destination folder of your release version is work

edited Sep 26 '19 at 03:20

answered Aug 22 '19 at 03:17

justnoone

111
2
5

3dmg · Answer 15 · 2019-08-27T11:57:03.620

3

The solution for me was to delete all files and folders from the apk output folder. I had this problem when creating a signed apk for a "production" flavor and the output.json in the "feature" output folder causes the problem -> Android Studio 3.6 Canary 7 showed me the correct error message. It is also working now for AS 3.5 stable with Gradle Plugin 3.5.0.

edited Aug 27 '19 at 11:57

answered Aug 27 '19 at 08:52

3dmg

718
1
9
19

pool · Answer 16 · 2019-08-28T09:32:05.127

3

All the solutions didn't work with me
In my case from AndroidStudio 3.4+ update to 3.5.
And finally I solve it by modify 'Destination Folder' to "app/build/outputs/apk"
detail pic

edited Aug 28 '19 at 09:32

answered Aug 28 '19 at 09:23

pool

31
2

score 3 · Answer 17 · answered May 07 '20 at 21:07

The solution :-

1- Build -> Clean Project didn't help

2-Build -> Make Project didn't help

3- restart android studio didn't help

4- Manually remove Build folder from app and project didn't help

the only solution for me was to remove all old builds from destination folder

score 2 · Answer 18 · answered Oct 21 '19 at 17:00

2

Manually delete all the exiting build variant folder as well build folder in project folder worked for me.

answered Oct 21 '19 at 17:00

Thamilvanan

189
4
17

Masoud Mokhtari · Answer 19 · 2019-10-29T07:38:01.737

2

Usually this issue happen on updating android Studio V3.4 to V3.5. Try to delete debug/output.json and release/output.json files.

Then Try these steps:

Step 1: Clean Project(Build > Clean Project)

Step 2: Rebuild Project(Build > Rebuild Project)

edited Oct 29 '19 at 07:38

answered Oct 22 '19 at 05:29

Masoud Mokhtari

2,390
1
17
45

score 2 · Answer 20 · answered Nov 05 '19 at 07:12

2

I have android studio 3.5.1 . For me below steps are worked

File -> Invalidate Caches/Restart
After android studio restarted click on Build -> Clean project
Then Build -> Rebuild Project

answered Nov 05 '19 at 07:12

Sachin Tanpure

1,068
11
12

score 1 · Answer 21 · answered Jun 27 '19 at 12:31

In my case build and launch project with different build configs was successful. But generating signed apk throws error Cause: buildOutput.apkData must not be null on the other hand apk was generated and Build Output toggle view prints BUILD SUCCESSFUL. Manual installation ends with message App not installed. My fault was using compileSdkVersion 'android-P' and after changing to compileSdkVersion 28 all goes well.

score 1 · Answer 22 · answered Aug 25 '19 at 04:40

I've tried all solutions and non of them helped! finally after many trying, I figured it out, just follow the tips:

copy your signature keystrok (that you use to release) inside yourProject/app/

gradle.properties (modify values related to your own key):

MYAPP_RELEASE_STORE_FILE=KEYSTROK_NAME
MYAPP_RELEASE_KEY_ALIAS=KEY_ALIAS
MYAPP_RELEASE_STORE_PASSWORD=R_PASS
MYAPP_RELEASE_KEY_PASSWORD=K_PASS
android.enableR8=true

app level build.gradle (inside android):

signingConfigs{
    release{
        if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
            storeFile file(MYAPP_RELEASE_STORE_FILE)
            storePassword MYAPP_RELEASE_STORE_PASSWORD
            keyAlias MYAPP_RELEASE_KEY_ALIAS
            keyPassword MYAPP_RELEASE_KEY_PASSWORD
        }
    }
}

configurations {
    cleanedAnnotations
    compile.exclude group: 'org.jetbrains' , module:'annotations'
}

app level build.gradle (inside buildTypes):

release {
    manifestPlaceholders = [analytics_deactivated: "false"]
    minifyEnabled true
    signingConfig signingConfigs.release
    useProguard true
    proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}

5. finally this command:

mac: ./gradlew clean assemble_YOUR_FAVOR_Release

win: gradlew clean assemble_YOUR_FAVOR_Release

where _YOUR_FAVOR_ is your optional favor, if you are not using any favor, just simply use assembleRelease instead of assemble_YOUR_FAVOR_Release

score 1 · Answer 23 · edited Sep 06 '19 at 14:27

1

This issue happens after update my Android studio v3.4 to v3.5 Now, it is working fine

I fixed this issue by deleting debug/output.json and release/output.json files

Android Studio 3.5 compilesdkVersion 28

apk generating working

edited Sep 06 '19 at 14:27

Jordan Kasper

13,153
3
36
55

answered Sep 06 '19 at 13:46

Pradeep P

221
1
2

score 1 · Answer 24 · edited Sep 08 '19 at 01:52

1

I was also annoyed by the same bug. But changing my Signed apk destination from c/users/project/app to c/users/project worked for me.

edited Sep 08 '19 at 01:52

Hadi GhahremanNezhad

2,377
5
29
58

answered Sep 07 '19 at 16:34

Sarthak Sharma

11
1

score 1 · Answer 25 · answered Oct 20 '19 at 11:47

1

1- Delete all generated app bundles (.aab) and APKs for all variants.

2- Delete the build folder

3- clean project

answered Oct 20 '19 at 11:47

Islam Assi

991
1
13
18

score 1 · Answer 26 · answered Oct 22 '19 at 04:53

1

Generate Signed APK for debug, and then you can generate signed APK for release.

answered Oct 22 '19 at 04:53

Dita Aji Pratama

710
1
12
28

You can't generate "Signed debug APK" – Farid Nov 09 '20 at 13:46
You can sign your debug build https://developer.android.com/studio/publish/app-signing#debug-mode – Dita Aji Pratama Nov 11 '20 at 04:30

score 0 · Answer 27 · answered Jul 16 '19 at 06:48

0

Seems cleaning the project may resolve the issue, but for me it worked like this.

File->sync project with gradle files.

answered Jul 16 '19 at 06:48

brahmy adigopula

617
3
15

score 0 · Answer 28 · answered Sep 28 '20 at 11:04

AS 4.0.1 (installed via snap)

Ubuntu 18.04 lts

configuring builds via build variant.

Combinations of invalidate cache / build / clean etc didnt help on their own, the only thing that helped was to switch build the active build variant back to armDebug and clean / rebuild after that.

Once I switched back to the desired variant I could build correctly.

Dulaj Madusanka · Answer 29 · 2022-02-16T05:18:19.673

0

enter code hereIf your using different build variants, Select the specific folder to generate signin apk file. When you are trying to generate signin apk flow, you can change the path. For me, this worked.

edited Feb 16 '22 at 05:18

answered Feb 09 '22 at 09:51

Dulaj Madusanka

308
2
17

score 0 · Answer 30 · answered Nov 25 '22 at 10:22

0

In my case, the path was pointing to e: drive and other solutions didn't work for me. I did:

Change the path
The path must be in the c: drive

It solved the problem

answered Nov 25 '22 at 10:22

Oriol Roma

329
1
5
9

Cause: buildOutput.apkData must not be null

30 Answers30

5. finally this command:

Linked