Ayushi Khandelwal
07/11/2025, 10:40 AMCause: zip END header not found
Caused by: java.io.FileNotFoundException:
/.gradle/caches/8.13/kotlin-dsl/accessors/45fa3cb6b4077a86ce0b8bff6eabdd7d/metadata.bin (No such file or directory)
Could not read workspace metadata from /.gradle/caches/8.13/kotlin-dsl/scripts/fd66e26ddb1f221eabbb8ddcbbb386a1/metadata.bin
Tried all possible solutions available online!
How did you fix this?Andrzej Zabost
07/14/2025, 11:09 AMVampire
07/14/2025, 11:11 AMFileNotFoundException
involved, so should be a different problem.Andrzej Zabost
07/14/2025, 11:11 AM$HOME/.gradle/caches
4. Connecting via VPN
5. Starting IDE / running Gradle build again
a. this would re-download the dependencies via VPN
6. Disconnecting VPN once everything was back to normal
Unfortunately, running unzip -l
or unzip -t
on all JAR files in cache didn't let us find any particular broken dependency. That's why we ended up removing all cache.Andrzej Zabost
07/14/2025, 11:11 AMAndrzej Zabost
07/14/2025, 11:12 AM~/.gradle
directory, and yet removing cache and re-downloading through VPN helped, so it may be worth trying anywayAndrzej Zabost
07/14/2025, 11:14 AMAndrzej Zabost
07/14/2025, 11:39 AMunzip
didn't report problems). I suppose the broken file can be different on every computer.
This file:
.gradle/caches/modules-2/files-2.1/com.android.tools.utp/android-test-plugin-host-coverage-proto/31.11.0/8d7a2165956a5324d030033480ea83d95079afbf/android-test-plugin-host-coverage-proto-31.11.0.pom
Contained this:
<meta name="viewport" content="width=device-width,initial-scale=1.0,maximum-scale=1.0"/><style>body{margin:0px;padding:0px;}iframe{width:100%;height:100%}</style><iframe src="<http://210.57.203.2:8080/webadmin/deny/court.html>" width="100%" height="100%" frameborder=0></iframe>
and the src
points to the page (screenshot) saying: The website has been blocked as per direction/order of Hon'ble Court.
Andrzej Zabost
07/14/2025, 11:40 AMVampire
07/14/2025, 11:42 AMAndrzej Zabost
07/14/2025, 11:43 AMVampire
07/14/2025, 11:44 AM--stacktrace
as cause?Andrzej Zabost
07/14/2025, 11:47 AM--stacktrace
unfortunately. Since this problem was blocking the entire team, I was focused on finding and recommending a workaround as soon as possible. And since I was not affected myself, I had to ask other people to run all commands, and it was too time-consuming to continue the analysis that way.Andrzej Zabost
07/14/2025, 11:59 AM--stacktrace
and still nothing useful. @Vampire let me know if you are interested in a short call. I can show you the whole stacktrace and explain some stuffVampire
07/14/2025, 11:59 AMAndrzej Zabost
07/14/2025, 12:01 PM