Reputation: 324
Today I updated my Android Studio to 2.0 and when I run my project is gives me this error
Error:Execution failed for task ':app:clean'.
> Unable to delete directory: /media/dev1/08782A6D782A5A281/workspace/gengold/GenGold/app/build/intermediates/exploded-aar/com.android.support/appcompat-v7/21.0.3/jars
This is my build.gradle
apply plugin: 'com.android.application'
android {
compileSdkVersion 21
buildToolsVersion "21.1.2"
defaultConfig {
applicationId "com.mobile.gengold"
minSdkVersion 15
targetSdkVersion 21
}
buildTypes {
release {
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
productFlavors {
}
}
dependencies {
compile 'com.android.support:support-v4:21.0.2'
compile 'com.android.support:appcompat-v7:21.0.3'
/*compile 'com.google.android.gms:play-services-maps:6.5.+'*/
compile 'com.google.android.gms:play-services:6.5.87'
compile files('libs/jncryptor-1.2.0.jar')
}
I have deleted the jars from that directory but it shows the error repeatedly. Also it creates the directory again.
Upvotes: 26
Views: 77734
Reputation: 1983
In my case in Windows I killed all OpenJVM processes in Windows Process Magager, then I was able to remove the directory. After next run it worked with no issues.
Upvotes: 0
Reputation: 360
In my case it was solved by running android studio as administrator, doing this did not give me that error again.
Upvotes: -1
Reputation: 21
Go app folder and delete build folder. After that go android studio and run. It should be fixed.
Upvotes: 2
Reputation: 1
In my case, the problem was due to prohibited character (') in strings.xml. Once I deleted ('), this problem was solved.
Upvotes: 0
Reputation: 21
In my case, the dependencies file was locked by Dropbox. Problem was solved after I stopped dropbox syncing service.
Upvotes: 0
Reputation: 51
There is a folder called mergdebugassets
.
In our case,
This could solve the problem with whatever was the folder in your case.
Upvotes: 1
Reputation: 2710
It states that Android Studio doesn't has the privilege to delete the directory.
Simply right on your project folder in windows explorer -> properties -> Security -> Edit -> here provide the necessary privilege like in my case added full control to my user that was logged in the Windows system.
Upvotes: 1
Reputation: 304
I was having the same problem and installed LockHunter and deleted the folder forcefully. None of the above solution worked for me so this is what I did.
Upvotes: 0
Reputation: 55
I had the same problem. In my situation I install the android studio at D folder and copy paste the projects folder to the same folder of android instalation
Solution
Move your projects folder out of the android folder.
Upvotes: 0
Reputation: 613
For me:
Open the command prompt and type taskkill /F /IM java.exe
. This will kill all java TM processes automatically.
Upvotes: 14
Reputation: 9
I had same problem in Android Studio 3.6. I was unable to delete the build folder so I renamed it and it worked for me.
Upvotes: -2
Reputation: 11
Try to make the usage of the “file smash” function from tencent qq pc manager. The manager can unlock the file and then delete it.
Where to use it? After you install QQ pc manager, choose tool kits and install "file smash" tool. And then choose the file to delete, press right key of mouse and you find the function to unlock file and delete it.
That works for me. I guess other pc manager like qq manager may have this function too. That's all.
Upvotes: 0
Reputation: 1117
After weeks of searching, I've found out that my Cloud-Sync-programs (I am using Tresorit, but same would apply to Dropbox or Google Drive aso) locked the files that AndroidStudio was trying to delete while uploading them to the cloud storage - and therefore making it impossible for AndroidStudio to delete the files.
On some cloud storage programs, you may use path filters - simply exclude the "build"-directories from your cloud storage (you usually dont need them backupped either way), or pause your cloud sync while working on the project.
Upvotes: 4
Reputation: 149
I'm using Android Studio 2.3.3 on windows, had the same problem, tried deleting the folder and got Access denied, rebooting my computer did not help either, for me the solution was : In Android Studio > File > Invalidate Caches / Restart...
Upvotes: 11
Reputation: 3544
For me, rebooting my computer unlocked the locked file and solved the problem.
Upvotes: 4
Reputation: 41
I noticed this started happening after I installed Tortoise SVN. I think installing it using a non-admin Windows account, might be the root of the issue.
Upvotes: 3
Reputation: 281
I have exactly the same problem. The only temporary solution I've found is to exit Android Studio, delete the entire "build" folder (not only the jars), and then getting back to Android Studio to Build it.
The first build goes without errors or any warnings, but to rebuild again you need to follow the same steps as before :(
This is not a solution, obviously, but seems like the problem comes out from any service keeping occupied the files to be deleted in the "Clean" part of the rebuilding process.
EDIT:
It seems there is a problem with NTFS file system in android 2.0 Check out in https://code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Status%20Priority%20Owner%20Summary%20Stars%20Reporter%20Opened&groupby=&sort=&id=206219
Upvotes: 19
Reputation: 61
i'm using android studio 2.0 and ubuntu 14.04 64bit.
i have the same problem, i just delete directory under ../app/build/intermediates/exploded-aar/com.android.support/
it works, i can run my project, but it will be showed again in the next running.
Upvotes: 6