Android Studio 3.1 "Run" not compiling code

Asked 27/3, 2018 at 6:39 Answered 8/2 at 14:38

Solved android android-studio android-gradle-plugin

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

Demirep answered 27/3, 2018 at 6:39 Comment(3)

Build -> Clean Project->Rebuild Project – Chaise 27/3, 2018 at 6:42

@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? – Demirep 27/3, 2018 at 6:44

Check this link for answer: https://mcmap.net/q/103850/-android-studio-3-1-run-command-does-not-rebuild-the-apk-duplicate – Freed 27/3, 2018 at 9:15

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.

Ungracious answered 27/3, 2018 at 6:49 Comment(7)

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. – Drusi 27/3, 2018 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) – Christi 28/3, 2018 at 10:54

@Christi It's working for me. Can you please check your project's other gradle's configuration. I think that would be issue. – Ungracious 28/3, 2018 at 11:25

@Christi Yes, Exactly. Currently in my configuration instant run is turned off. So this solution works for me. – Ungracious 28/3, 2018 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. – Mendiola 23/4, 2019 at 20:7

I had this issue in latest AS 4.2 Canary build for long time. This fixed that issue, thanks. – Bubal 5/10, 2020 at 14:59

Good! My AS4.1.2 new project still have this issue. Really weird. – Auramine 18/3, 2021 at 14:3

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.

Chaise answered 27/3, 2018 at 6:49 Comment(10)

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. – Ungracious 27/3, 2018 at 6:57

@SaguKacha Indeed. – Chaise 27/3, 2018 at 7:39

@Christi Whats your buildToolsVersion ?? – Chaise 28/3, 2018 at 11:7

@IntelliJAmiya 26.0.2 – Christi 28/3, 2018 at 11:15

@Christi compileSdkVersion 27 buildToolsVersion "27.0.3" then Clean-Rebuild and run – Chaise 28/3, 2018 at 11:37

@IntelliJAmiya same result with compileSdkVersion 27 buildToolsVersion "27.0.3" – Christi 28/3, 2018 at 11:54

@Christi Gradle version 3.0.1 ? – Chaise 28/3, 2018 at 11:55

@Christi Disable Instant run ?? – Chaise 28/3, 2018 at 11:55

@IntelliJAmiya this is the problem: I NEED instant run :(( "run" works with instant run disabled – Christi 28/3, 2018 at 11:57

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.

Strader answered 27/3, 2018 at 6:42 Comment(5)

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. – Demirep 27/3, 2018 at 6:47

did you try step 2? go to your project folder and delete all build folder with module build folder. – Strader 27/3, 2018 at 6:50

Yes I did delete the build folder as well, nothing works! – Demirep 27/3, 2018 at 6:51

desable instan run and do all agiain. – Strader 27/3, 2018 at 6:52

did you get solution? – Strader 27/3, 2018 at 6:56

I encountered the same issue with Iguana | 2023.2.1 beta 02. While I was able to build my project without any warnings or clear errors, my app would not run. I could create a bundle or APK in the APK folder, but I couldn't run my project on an emulator or a device that didn't already have an installed APK of the same project. I attempted all the suggested solutions, but none of them worked for me. In the end, I decided to downgrade Android Studio to the earliest stable version available, which is Hedgehog | 2023.1.1. This resolved my problem.

Eton answered 8/2 at 14:38 Comment(0)

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

Freed answered 10/4, 2018 at 5:58 Comment(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.

Dimarco answered 14/1, 2021 at 16:42 Comment(0)

Hot tags

Godot Unity Godot Help Programming Godot 4.X GUI GDScript 3D 2D Physics CSharp Godot 3.X VR XR Projects C++

Recommended topics

Hot tags