<#C19FD9681|> <#C014NQAJUUW|> Since, yesterday all...

# gradle

[lokesh jonwal]

#C19FD9681 #C014NQAJUUW Since, yesterday all of the gradle command are resulting in failure saying :
A problem occurred configuring root project .
> java.util.zip.ZipException: zip END header not found

Then I ran this command to figure out which file is corrupt.
find ~/.gradle/caches -type f -name ".jar" -exec unzip -t {} \; | grep "End-of-central-directory signature not found"*

and found that this file has problem :

~/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin.jvm/org.jetbrains.kotlin.jvm.gradle.plugin/1.9.24/5e99c377627e50c47eedcd8e038a8b2fc0dd9fe0/org.jetbrains.kotlin.jvm.gradle.plugin-1.9.24.jar

We also repeated the same activity after deleting the entire ~/.gradle folder, but the same error message is still haunting us. Our entire team is facing the same issue without making any changes to the code and everything was working fine till Friday.

Please find the gradle scan at https://scans.gradle.com/s/sf44kerxpyah4

[Vampire]

I probably just told a colleague of yours on the Gradle Slack.
Maybe the corruption is not local but on some repository proxy you use, or similar.

[Vampire]

https://github.com/expo/expo/issues/34613 and https://lraman.com.np/blogs/react-native-gradle-plugin-build-error/ blame R/N to somehow have caused this and suggest steps to resolve it. But from your Scan it does not seem like you use R//N. Except if you use it in another project and it still is the cause. 🤷‍♂️

[gammax]

Hey, it’s Nicola here from Meta. I maintain the React Native Gradle Plugin.
@Vampire could you elaborate on why you feel this is to blame on React Native’s end?

Specifically we had users globally with their build starting to fail if they’re depending on Kotlin 1.9.24. The issue doesn’t occur if users are on Kotlin 1.9.25

This started happening on Monday, and we haven’t released any version of our libraries at all in the meanwhile.

[Vampire]

Hi there. :-)
It was not me.
If you read my message carefully, I said those issues are blaming R/N. 🙂

Kotlin 1.9.24 was released month ago too, so depending 1.9.25 most probably just causes getting fresh files from the server and thereby fixing the corruption as the corrupt files are no longer used. 🤷‍♂️

In the specific case of the user asking here and his colleagues asking on the Gradle Forum and in the Gradle Community Slack, the problem seems to be something different actually, they have a JAR in their cache for the K/JVM plugin marker artifact which does not even have a JAR and the content is an iframe with some error message, so it is most probably more some mirror misbehaving or whatever that delivers non-sense content it shouldn't deliver.

[Vampire]

For anyone following from India here, the ministry of electronics in India caused the Kotlin Gradle Plugin URLs of 1.9.24 to be blocked.
This causes the "this is blocked" HTML page to be downloaded as jar file as the blocking is not accompanied with an according HTTP status response, which can then not be read by Gradle as jar file of course.
Update KGP version to 1.9.25 and it should work. (Until they block that too eventually)

[tapchicoma]

Do you know the reason of such block?

[gammax]

Nope not really

[Vampire]

No, but if you open the ill jar file as website in a browser, you see the message that the ministry caused the page to be blocked