0
1.1K
VistasCaused by: java.lang.AssertionError: Could not delete caches dir yourProject\build\kotlin\compileDebugTestingKotlin
Sometimes this unexpected message appear and the only way to deal with this is to restart the pc and when it starts again go to the obove path and delete the file before start Android Studio with the project. It works for some time but latter appears again. Maybe someone of you know how deal better with this annoying issue.
CreateProcess error=206, El nombre del archivo o la extensión es demasiado largo
Caused by: java.lang.AssertionError: Could not delete caches dir YourProjectPath\build\kotlin\compileDebugTestingKotlin
8 Respuestas
Responde la pregunta0
invalidating cache and restarting worked for me
0
ext.kotlin_version = '1.4.10'
classpath 'com.android.tools.build:gradle:4.0.1'
distributionUrl=https://services.gradle.org/distributions/gradle-6.1.1-all.zip
update all version
0
I'm using Android Studio version Arctic Fox 2020.3.1 and I got the same error. In order to fix it, we need to kill the process Java.exe
0
In windows open task manager CTRL + ALT + DEL
You can see java.exe on the details page.
End Task for all instances of Java.exe
0
Updating project level build.gradle from:
classpath 'com.android.tools.build:gradle:4.1.1'
to:
classpath 'com.android.tools.build:gradle:4.2.1'
solved my issue. If it won't fix yours you can also try to update:
ext.kotlin_version = '1.4.32'
Hope this will work for you.
0
Try reopening Android Studio and clean your project. Worked for my cache issue.
0
In windows open task manager.
- Go to details tab.
- Look for Java.exe.
- End Task for all instances of Java.exe.
This works perfectly for me.
0
Notice: This happens with the newer AndroidStudio 4.2.x.
Temporary solution:
Delete (the contents of) the folder which is giving you the issue. For example:
..\app\build\kotlin\compileDebugKotlin\caches-jvm\inputs
If you get: "The file is open in OpenJDK Platform Binary" you'll need to stop these processes through Windows Task Manager > Details > Java.exe.
Please know that with this method the error will repeat again after several assembly attempts.
UPDATE:
Google hasn't provide us a fix, so you'll need to downgrade to an older version which works for you. 4.1.3 seems to be working fine.