The APK file does not exist on disk

AndroidAndroid StudioApk

Android Problem Overview


When I am trying debug application on Android Studio gives this log output :

> The APK file > /Users/MyApplicationName/app/build/outputs/apk/app-debug.apk does not > exist on disk.

I restarted Android Studio, but I can't solve this problem . How can I solve it ? Thank you

Android Solutions


Solution 1 - Android

Click this option to solve the error:

Run: View > Tool Windows > Gradle > [project] > Tasks > build > build

Solution 2 - Android

If you are facing this issue after the update to Android Studio V 3.1 then try the below.

I was facing this same problem when I updated to Android Studio 3.1. All other solutions I found here were quite manual because you have to clean and rebuild every time, that is not good at all. But thanks to Iman Marashi's answer here I was able to solve it.

Go to Run -> Edit Configurations...

Make sure you have a "Gradle-aware Make" on the Before launch section:

Run/Debug Configurations

To add it click the + sign and select Gradle-aware Make and a popup will appear, just leave the text field empty and click OK and OK.

Solution 3 - Android

In my case, executing "Sync Project with Gradle Files" helped. Neither restarting Andoid Studio nor clearing the cache did anything.

Solution 4 - Android

If you just want to know the conclusion, please go to the last section. Thanks.

Usually when building project fails, some common tricks you could try:

  • Build -> Clean Project
  • Check Build Variants
  • Restart Android Studio (as you mentioned)

But to be more specific to your problem - when Android Studio could not find the APK file on disk. It means that Android Studio has actually successfully built the project, and also generated the APK, however, for some reason, Android Studio is not able to find the file.

In this case, please check the printed directory according to the log. It's helpful.

For example:

With Android Studio 2.0 Preview (build 143.2443734).

  1. Checkout to a specific commit (so that it's detached from head): git checkout [commit_hash]

  2. Run project

  3. Android Studio tells: The APK file /Users/MyApplicationName/app/build/outputs/apk/app-debug-HEAD.apk does not exist on disk

  4. Go to the directory, there is a file actually named: app-debug-(HEAD.apk (with an extra parenthesis)

  5. Run git branch

    *(HEAD detached at 1a2bfff)

So here you could see, due to my gradle build script's mistake, file naming is somehow wrong.

Above example is just one scenario which could lead to the same issue, but not necessary to be the same root cause as yours.

As a result, I strongly recommend you to check the directory (to find the difference), and check your build.gradle script (you may change the apk name there, something like below):

applicationVariants.all { variant ->
        variant.outputs.each { output ->
            def newFileName = "whatever you want to name it";
            def apk = output.outputFile;
            output.outputFile = new File(apk.parentFile, newFileName);
        }
    }

Solution 5 - Android

Make sure that you don't have apostrophe or & in your path

Solution 6 - Android

Make sure that there is Grading-aware Make in Run/Debugging configurations >> before launch section :

Like this image

Solution 7 - Android

I witnessed a similar issue usually when I'm switching git branches. For me shutting down Android Studio rm -rfv ~/Library/Caches/AndroidStudio* and restart Android Studio is the ticket.

Solution 8 - Android

In Android Studio 3.1.1 select File | Sync Project with Gradle Files.

In Android Studio 3, select File | Synchronize.

Then run your project again.

Solution 9 - Android

The year is 2018. Android Studio version is 3.2.0 alpha3 and we still get this problem. As none of the above worked for me, here is my 2 cents:

Every time this happens I just generate the apk from command line:

gradlew assembleDebug

UPDATE

Deleting the folder .AndroidStudio[version] and losing all your preferences and caches... seems to solve the problem

Solution 10 - Android

In my case, I was using a special character in my app file path. I closed the Android Studio and removed the ' character from my app file path. Everything worked fine when I reopned the project.

Solution 11 - Android

I've solved building an apk using the Build option from the top window and Build APK. No need to do something weird.

Solution 12 - Android

For Unix like users (Linux/MacOs X), instead of removing ~/.gradle/caches/, in command line do :

$ cd path_to_you_project
$ touch build.gradle

Then ask Android Studio to build APK, it will reset gradle cache itself.

Solution 13 - Android

My problem is that I was appending the version number to the APK. Changing the version number and re-syncing Gradle fixed the problem for me.

def appendVersionNameVersionCode(variant, defaultConfig) {
    variant.outputs.each { output ->
        if (output.zipAlign) {
            def file = output.outputFile
            def removeApp = file.name.replace("app-", "")
            def removeType = removeApp.replace("-release", "")
            def fileName = removeType.replace(".apk", "." + defaultConfig.versionName + ".apk")
            output.outputFile = new File(file.parent, fileName)
        }

        def file = output.packageApplication.outputFile
        def removeApp = file.name.replace("app-", "")
        def removeType = removeApp.replace("-release", "")
        def fileName = removeType.replace(".apk", "." + defaultConfig.versionName + ".apk")
        output.packageApplication.outputFile = new File(file.parent, fileName)
    }
}

Solution 14 - Android

> Build ---> Build APK(s) and be sure it works

Solution 15 - Android

File -> Invalidate Caches / Restart

Solution 16 - Android

If you tried all the above answers and it didn't work try to disable "Instant Run" feature. This one helped me after all attempts.

File -> Settings -> Build, Execution, Deployment -> Instant Run -> Uncheck checkbox there

Solution 17 - Android

I also got that issue, after cleaning the build. For me solution was I just sync the gradle and it worked for me.

Solution 18 - Android

In my case the problem was that debugging configuration become invalid somehow, even that the test method name, class or package has not changed.

I deleted the configurations from Run->Edit Configurations, at here:

enter image description here

Android studio will create a new one automatically.

Solution 19 - Android

Sync, Clean, Rebuild and Invalidate Cache and Restart

None of them worked for me.

I have deleted the APK and output.json files in the release folder and debug folder and then tried sync, clean, and build, then it worked fine.

OR simply Delete folder which has the apk and output.json file (in case of debug/ release)

Solution 20 - Android

Faced the same issue with gradle 1.5

I had to clean the build files: > Build -> Clean project

And build an APK to force the full compilation and sync of the gradle files: > Build -> Build APK

I still don't know why or how it happened tho.

Solution 21 - Android

if you are using Linux, try setting write permission to the app/build folder.

Solution 22 - Android

i had the same problem. it was due to false name in the path. there was a special Character in the path like this: C:\User\My App\Projekte-Tablet&Handy i deleted the "&" character and it worked well.

Solution 23 - Android

My problem was including minutes in the file name - it looked for appname_debug_0.9.0.1_170214_2216.apk when the generated file was appname_debug_0.9.0.1_170214_2217.apk so the output filename code (nabbed from elsewhere) was clearly being called from two different points in the build.

applicationVariants.all { variant ->
        variant.outputs.each { output ->
            def project = "appname"
            def SEP = "_"
    //        def flavor = variant.productFlavors[0].name
            def buildType = variant.variantData.variantConfiguration.buildType.name
            def version = variant.versionName
            def date = new Date();
            def formattedDate = date.format('yyMMdd_HHmm')

            def newApkName = project + SEP + /*flavor + */ SEP + buildType + SEP + version + SEP + formattedDate + ".apk"

            output.outputFile = new File(output.outputFile.parent, newApkName)
        }
    }

Solution 24 - Android

The problem for me was that somehow it could really not find the apk, while the apk exists.

The APK file /Users/Paul/AndroidStudioProjects/android-tv-launcher/ui/build/outputs/apk/nameofapk.apk does not exist on disk.
Error while Installing APK

All I had to do, was right click on the apk-copy relative path, and just

adb install -r <paste of relative path>

And the apk was installed and good to go. This issue happened on OSX for me.

Solution 25 - Android

Solved in may of 2018 with the new Android Studio 3.1. Delete the .gradle, .idea and build directories inside your app folder. Then try to run it again and you won't see the error.

Solution 26 - Android

I change build.gradle file a litle info,and click "Sync Now",just ok.

Solution 27 - Android

Remove the directory ~/.gradle/caches/. It's OK to do this while Android Studio is opened. (Refer pm installing wrong package name) Press "Sync project with Gradle files" icon on Android Studio Run the project and the remote path will be correct.

Refer answer @ https://stackoverflow.com/questions/22155938/android-studio-gets-package-name-wrong-when-running-apk

Solution 28 - Android

Make sure that in the path generated in your logs -in your case: > /Users/MyApplicationName/app/build/outputs/apk/app-debug.apk

folder "outputs" indeed has an "apk" folder.

That was my problem, if it's not there, you will need to run the "assembleRelease" task in gradle by following the below screenshot;

[![Steps to run the gradle assembleRelease task][1]][1] [1]: http://i.stack.imgur.com/3nPDu.png

Then the folder will be generated.

Solution 29 - Android

Nothing above helped me, but I figured this out by switching to another flavor in the Build Tools panel and then switching back to the needed one.

Solution 30 - Android

modify the file:build.gradle(app directory). in fact:you should not change this file , only by this to get sync tips,then sync project.

Solution 31 - Android

The button is called "Sync Project with Gradle Files" and it looks alike: Gradle Sync... always need to click it, when updating the version number, which is resulting in another APK filename (unless the filename has not changed, installing the package always works, which hints for, that the filename is being cached). The equivalent Gradle CLI option appears to be --recompile-scripts.

@see Appendix D. Gradle Command Line.

Solution 32 - Android

First remove cleaner by going to edit configuration, It may be cleaning the build after building the apk.

Click on edit from set run/debug then click on gradle list select the clean project item and then click on -(top 2nd from left).

Solution 33 - Android

Using Android Studio 2.2.1, I clicked the Sync Project with Gradle Files option, from the dropdown at the top, Tools>Android

Similar, to an answer posted above, see below for a screenshot of how to get to this option.

enter image description here

Solution 34 - Android

    1) This problem occure due to apk file .if your apk file
        (output/apk/debug.apk) not generated in this format . 

    2) you should use always in gradle file .
    
    buildTypes {
            release {
                minifyEnabled false
                proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
            }
        }

Solution 35 - Android

I got it to work by:

  1. Closing the project
  2. From the Android Studio Welcome Window (or File > New), click on Import Project.

I guess that forced it to reinstall the APK, and now everything is running fine.

Solution 36 - Android

i solved this app by doing

  1. First Build - > Build Apk(s)
  2. Run the app now

if it not worked do Clean and build the project and then do again 1 & 2.

Solution 37 - Android

I tried all of these things and none of them worked. I ended up having to do a couple of these things are the same time. Very frustrating that it took this much time.

The problem I had was related to running my unit tests following the upgrade to AS 3.1.

Here is what I did... 1.) Run / Edit Configurations / Select Tests.... 2.) Add options to "Gradle-aware Make" 3.) Select check box "Skip installation if ADK has not changed" on Misc tab

Good luck.

Solution 38 - Android

Go to Build option on the top bar of android studio>create 'Build APK(s)', once build has created, open the folder where it has available(app\build\outputs\apk) then close the folder, that's all....then try to install the app.

Solution 39 - Android

Solved this issue by updating the Android SDK-Build Tools.

Solution 40 - Android

in my case, just

> View > Tool Windows > Gradle > right click [project] > Refresh Gradle Project

Solution 41 - Android

assemble[Variant] would generate the APK for you on disk although it should not be necessary to use it to debug the app.

Run the following command in the root directory of the project:

$ ./gradlew clean build assemble[Variant]

GL

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionyusufonderdView Question on Stackoverflow
Solution 1 - Android指尖上的AndroidView Answer on Stackoverflow
Solution 2 - AndroidSevenView Answer on Stackoverflow
Solution 3 - AndroidBartekView Answer on Stackoverflow
Solution 4 - AndroidJing LiView Answer on Stackoverflow
Solution 5 - AndroidRim GazzahView Answer on Stackoverflow
Solution 6 - AndroidIman MarashiView Answer on Stackoverflow
Solution 7 - Androiduser213493View Answer on Stackoverflow
Solution 8 - Androidlive-loveView Answer on Stackoverflow
Solution 9 - AndroidAndroidersonView Answer on Stackoverflow
Solution 10 - AndroidImmortal CodeView Answer on Stackoverflow
Solution 11 - AndroidMun0nView Answer on Stackoverflow
Solution 12 - AndroidJean-Marc DelafontView Answer on Stackoverflow
Solution 13 - AndroidLou MordaView Answer on Stackoverflow
Solution 14 - AndroidKadir altınokView Answer on Stackoverflow
Solution 15 - AndroiddvrmView Answer on Stackoverflow
Solution 16 - AndroidAnZView Answer on Stackoverflow
Solution 17 - Androidu_pendraView Answer on Stackoverflow
Solution 18 - AndroidMiguelSlvView Answer on Stackoverflow
Solution 19 - AndroidGiridharaSPKView Answer on Stackoverflow
Solution 20 - AndroidSimon PAView Answer on Stackoverflow
Solution 21 - AndroidCatalin ClabescuView Answer on Stackoverflow
Solution 22 - AndroidOrientosView Answer on Stackoverflow
Solution 23 - AndroidIan SpencerView Answer on Stackoverflow
Solution 24 - AndroidBoldijar PaulView Answer on Stackoverflow
Solution 25 - AndroidGerardo SuarezView Answer on Stackoverflow
Solution 26 - Android凤清云View Answer on Stackoverflow
Solution 27 - AndroidmaskView Answer on Stackoverflow
Solution 28 - AndroidAmgadView Answer on Stackoverflow
Solution 29 - AndroidDmytro KarataievView Answer on Stackoverflow
Solution 30 - Android兰坡阳View Answer on Stackoverflow
Solution 31 - AndroidMartin ZeitlerView Answer on Stackoverflow
Solution 32 - AndroidSonu KumarView Answer on Stackoverflow
Solution 33 - AndroidLee BrindleyView Answer on Stackoverflow
Solution 34 - AndroidpritiView Answer on Stackoverflow
Solution 35 - AndroidViren ModyView Answer on Stackoverflow
Solution 36 - Androidsaigopi.meView Answer on Stackoverflow
Solution 37 - AndroidRob BreideckerView Answer on Stackoverflow
Solution 38 - AndroidBISHWAJEETView Answer on Stackoverflow
Solution 39 - AndroidChristian SchulzendorffView Answer on Stackoverflow
Solution 40 - AndroidJenkynView Answer on Stackoverflow
Solution 41 - AndroidBraian CoronelView Answer on Stackoverflow