Has anyone experienced this weird behaviour when publishing KMP lib to bintray via maven-publish - along with the version you;re publishing, there are few "empty" versions created as well, one for each platform named not with semVer, but with artifact name... e.g. 1.0.0 vs my-lib-wasm32
Big Chungus
07/28/2020, 12:57 AM
Found the issue and fix
Copy code
# The following property is required to mitigate issue <https://github.com/gradle/gradle/issues/11412>.
systemProp.org.gradle.internal.publish.checksums.insecure=true
s
serebit
07/28/2020, 1:05 AM
Yep! I was the one who submitted that issue-- still waiting on Bintray to fix it đ
a
Arkadii Ivanov
07/28/2020, 7:28 AM
Yeah, spend 2 hours deleting these sha files last time âšī¸
b
Big Chungus
07/28/2020, 7:29 AM
I had custom post-publish task for each publication that was just sending a request to bintray api to delete those versions đ