Reputation: 8463
When I try to install an app, there are two possibilities:
app
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:
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!)Invalidate Caches/Restart
Upvotes: 91
Views: 24600
Reputation: 339
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.
Upvotes: 0
Reputation: 8464
I have solution for your issue.
Also confirmed by Android Studio on Twitter : https://twitter.com/androidstudio/status/981914632892960768
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.
Upvotes: 164
Reputation: 361
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.
Upvotes: 0
Reputation: 19240
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
Upvotes: 0
Reputation: 75788
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.
Upvotes: 6
Reputation: 496
clean your project and run again
If it's not work then
Upvotes: 2