Android Studio 3.1 "Run" not compiling code

Question

When I try to install an app, there are two possibilities:

Install existing APK from build folder when I run the app
Install APK after performing clean build

For existing APK in the build folder, the app just works fine. But when I clean the project using Build -> Clean Project, and then try to run the app (i.e. install the app to my emulator or physical device), it shows me error:

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

NOTE: This behaviour happens only when I clean the project and not when I have already have a pre-built app APK in my build folder

I've referred to: The APK file does not exist on disk but my point is, when we usually run the app after cleaning the project, we never need to make a build of it, if the APK is not existing in the build folder, it automatically generates and installs the latest one.

Things I've tried:

Running the app when APK file exists in the build folder (works perfectly fine)
Running the Clean Project -> Running the app (expected is the project would be built and the app would get installed but it shows the above mentioned error!)
Same process of cleaning and running the app after doing Invalidate Caches/Restart

@IntelliJAmiya exactly as you said, but the point here is, when I rebuild the project, it surely works, but shouldn't it generate the APK & work the same way if I run the app? — Sneh Pandya, Mar 27 '18 at 06:44
Check this link for answer: https://stackoverflow.com/a/49508278/3806413 — 0xAliHn, Mar 27 '18 at 09:15

score 161 · Accepted Answer · edited Dec 01 '21 at 08:54

161

I have solution for your issue.

Also confirmed by Android Studio on Twitter : https://twitter.com/androidstudio/status/981914632892960768

Edit your app configuration as below.

Here you can see your app configuration as below.

Here is missing Gradle-aware make attribute in before launch configuration. You can see here.

Please add this Gradle-aware Make attribute through this way. Click on + icon and select Gradle-aware Make as seen in this screen.

You can add this without writing any task just press OK button and task will be added and now it should look like this. Now apply changes and run your application.

It will solve this old apk installing issue on clean build in new Android Studio 3.1 issue.

Note : This issue is resolved in new Android Studio 3.1.1 Stable release.

edited Dec 01 '21 at 08:54

Nimantha

6,405
6
28
69

answered Mar 27 '18 at 06:49

Sagar Kacha

8,338
4
18
27

1

It seems that if you change your code and run the app, it's not building the app just running the old code. This solution worked for me. – Vicky Mar 27 '18 at 13:47
NOT WORKING: Shutdown finished in 0ms Error while generating dependencies split APK com.android.ide.common.process.ProcessException: Failed to execute aapt at com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:809) at com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:797) at com.android.build.gradle.internal.transforms.InstantRunSplitApkBuilder.generateSplitApkResourcesAp(InstantRunSplitApkBuilder.java:373) – android51130 Mar 28 '18 at 10:54
@android51130 It's working for me. Can you please check your project's other gradle's configuration. I think that would be issue. – Sagar Kacha Mar 28 '18 at 11:25
@android51130 Yes, Exactly. Currently in my configuration instant run is turned off. So this solution works for me. – Sagar Kacha Mar 28 '18 at 11:53
Running Android Studio 3.4 (built April 9, 2019), it was not generating instant_run_split_apk_resources files, and therefore not running. Only breaking for one of my Build Variants. The fix for me was to REMOVE Gradle-aware Make from the configuration's "Before launch" list. Now my "Before launch" list is empty, and it still works fine. – ubzack Apr 23 '19 at 20:07
1

I had this issue in latest AS 4.2 Canary build for long time. This fixed that issue, thanks. – muthuraj Oct 05 '20 at 14:59
Good! My AS4.1.2 new project still have this issue. Really weird. – Loyea Mar 18 '21 at 14:03

IntelliJ Amiya · Answer 2 · 2018-03-28T12:04:00.400

6

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

May be bug. You should change Settings.

You should open the Run/Debug Configurations dialog & select Run > Edit Configurations

Make sure, Gradle-aware Make is Added in TaskList or not. If not then click + & select from the options.

Note

If you receive

Shutdown finished in 0ms Error while generating dependencies split APK com.android.ide.common.process.ProcessException: Failed to execute aapt at com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:809) at com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:797) at com.android.build.gradle.internal.transforms.InstantRunSplitApkBuilder.generateSplitApkResourcesAp(InstantRunSplitApkBuilder.java:373)

You should Un-Check INSTANT RUN.

File-- Settings-- Build, Execution, Deployment -- Instant Run and uncheck Enable Instant Run.

edited Mar 28 '18 at 12:04

answered Mar 27 '18 at 06:49

IntelliJ Amiya

74,896
15
165
198

1

Yes, It will work in rebuild because configuration is already setup with instant run so. But will not work on clean build and run project combination. – Sagar Kacha Mar 27 '18 at 06:57
1

@SaguKacha Indeed. – IntelliJ Amiya Mar 27 '18 at 07:39
NOT WORKING: Shutdown finished in 0ms Error while generating dependencies split APK com.android.ide.common.process.ProcessException: Failed to execute aapt at com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:809) at com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:797) at com.android.build.gradle.internal.transforms.InstantRunSplitApkBuilder.generateSplitApkResourcesAp(InstantRunSplitApkBuilder.java:373) – android51130 Mar 28 '18 at 10:57
@android51130 Whats your `buildToolsVersion ` ?? – IntelliJ Amiya Mar 28 '18 at 11:07
@IntelliJAmiya 26.0.2 – android51130 Mar 28 '18 at 11:15
@android51130 `compileSdkVersion 27 buildToolsVersion "27.0.3"` then Clean-Rebuild and run – IntelliJ Amiya Mar 28 '18 at 11:37
@IntelliJAmiya same result with compileSdkVersion 27 buildToolsVersion "27.0.3" – android51130 Mar 28 '18 at 11:54
@android51130 Gradle version `3.0.1` ? – IntelliJ Amiya Mar 28 '18 at 11:55
@android51130 Disable `Instant run` ?? – IntelliJ Amiya Mar 28 '18 at 11:55
@IntelliJAmiya this is the problem: I NEED instant run :(( "run" works with instant run disabled – android51130 Mar 28 '18 at 11:57

score 2 · Answer 3 · edited Mar 27 '18 at 06:43

2

clean your project and run again

If it's not work then

Step 1 Close your project.
Step 2 Go to your project folder and delete all build folder.
Step 3 run your project.

edited Mar 27 '18 at 06:43

Vidhi Dave

5,614
2
33
55

answered Mar 27 '18 at 06:42

Vishal Sojitra

486
3
10

1

Also tried closing project, closing Android Studio & performing invalidate caches/restart but no luck, after cleaning the app, it always shows the error, and strangely, if the project is built, it always runs the same APK which is in build folder without updating with any changes. – Sneh Pandya Mar 27 '18 at 06:47
did you try step 2? go to your project folder and delete all build folder with module build folder. – Vishal Sojitra Mar 27 '18 at 06:50
Yes I did delete the build folder as well, nothing works! – Sneh Pandya Mar 27 '18 at 06:51
desable instan run and do all agiain. – Vishal Sojitra Mar 27 '18 at 06:52
did you get solution? – Vishal Sojitra Mar 27 '18 at 06:56

score 0 · Answer 4 · answered Apr 10 '18 at 05:58

This issue has been fixed with Android studio 3.1.1 (April 2018) release. Update your android studio to 3.1.1.

Here is there explanation regrading the issue details, cause and solution:

In some cases, when a project created in Android Studio 3.0 was opened for the first time in Android Studio 3.1, the Gradle-aware Make task was removed from the Before launch area in Run/Debug Configurations. The result was that projects did not build when the Run or Debug button was clicked, which in turn caused failures such as deployment of incorrect APKs and crashes when using Instant Run.

To solve this problem, Android Studio 3.1.1 adds the Gradle-aware Make task to the run configuration for projects that are missing this entry. This modification occurs after the first Gradle sync when the project is loaded.

Official release notes: https://developer.android.com/studio/releases/index.html#3-1-0

score 0 · Answer 5 · answered Jan 14 '21 at 16:42

0

For all people seing this and having the issue on Android Studio +4.0.0:

Run -> Edit configurations... -> disable check box (Allow parallel run)

It may slow your build a little but it better than running the app more than one time.

answered Jan 14 '21 at 16:42

Robert

353
3
12

Android Studio 3.1 "Run" not compiling code

5 Answers5

Linked

Related