Jitpack.io Checksum validation failed for 2.6.0

[runswithd6s]

We are relatively consistently getting "random" build errors due to checksum mismatches for 2.6.0. It appears that Jitpack has at least two different build artifacts that it is serving requests with. Sometimes it works for us, and sometimes it does not. This inconsistency has become quite painful.

Retrieving com/github/kenglxn/qrgen/javase/2.6.0/javase-2.6.0.jar from Jitpack
Retrieving com/github/kenglxn/qrgen/core/2.6.0/core-2.6.0.jar from Jitpack
Retrieving com/github/kenglxn/qrgen/core/2.6.0/core-2.6.0.jar from Jitpack
Could not transfer artifact com.github.kenglxn.qrgen:core:jar:2.6.0 from/to Jitpack (https://jitpack.io/): Checksum validation failed, expected 0c9d3c652d56b347b80e3e28eedd861ff8b9e552 but is 8eec5f8a5b67769b827b02b1b718a4373e448adb

Related: #137

[philipwhiuk]

We worked around this by disabling checksums but that's not a great solution. Might have to locally build our own copy to properly resolve it 😥

[runswithd6s]

Thanks for the suggestion, @philipwhiuk. We ended refactoring to use a different library.