Open ChaseGuru opened 3 weeks ago
Any update on this or does anyone know a suitable workaround?
This is currently blocking our Release Pipeline.
You can import .aar file to temporary solution fix the problem.
Download and put 6.1.0 aar file to project/lib
implementation the aar:
implementation files('../libs/usbserial-6.1.0-release.aar')
Switching back from 6.1.0 to version 6.0.6 worked for me.
Will fail to find com/github/felHR85/UsbSerial/7ad6c9f6/UsbSerial-7ad6c9f6.aar - correctly, because the actual artifact was: com/github/felHR85/UsbSerial/7ad6c9f6/UsbSerial-7ad6c9f6-release.aar
@ChaseGuru Hey, you can try below custom implementation, it works on my side.
implementation('com.github.felHR85:UsbSerial:7ad6c9f6') {
artifact {
name = 'UsbSerial'
classifier = 'release'
type = 'aar'
}
}
Will fail to find com/github/felHR85/UsbSerial/7ad6c9f6/UsbSerial-7ad6c9f6.aar - correctly, because the actual artifact was: com/github/felHR85/UsbSerial/7ad6c9f6/UsbSerial-7ad6c9f6-release.aar
@ChaseGuru Hey, you can try below custom implementation, it works on my side.
implementation('com.github.felHR85:UsbSerial:7ad6c9f6') { artifact { name = 'UsbSerial' classifier = 'release' type = 'aar' } }
On the same principle i created a MR to update the dependencies and build successfully on jitpack.
MR: https://github.com/felHR85/UsbSerial/pull/377 Dependency:
dependencies {
implementation 'com.github.angelix:UsbSerial:d5cf5314aa'
}
Will fail to find com/github/felHR85/UsbSerial/7ad6c9f6/UsbSerial-7ad6c9f6.aar - correctly, because the actual artifact was: com/github/felHR85/UsbSerial/7ad6c9f6/UsbSerial-7ad6c9f6-release.aar
@ChaseGuru Hey, you can try below custom implementation, it works on my side.
implementation('com.github.felHR85:UsbSerial:7ad6c9f6') { artifact { name = 'UsbSerial' classifier = 'release' type = 'aar' } }
Thanks, I'll try it now. I tried a configured implementation like that, but I didn't find the right combination of variables to get it to use the release artifact correctly.
Switching back from 6.1.0 to version 6.0.6 worked for me.
This is the workaround I did originally to get my deploy out.
For whatever reason, it seems like the cached build of 6.1.0 expired and jitpack ended up attempting to rebuild it on the 18th.
But that failed: https://jitpack.io/com/github/felHR85/UsbSerial/6.1.0/build.log
I referenced the latest commit hash instead to force jitpack to build that (since it doesn't seem to be retrying for 6.1.0)
That build artifacts successfully: https://jitpack.io/com/github/felHR85/UsbSerial/7ad6c9f6/build.log
Except, the artifacts seem to be different than before, and projects asking for the dependency find the package on jitpack, but still can't find the artifacts, just for different reasons now.
App's using:
Will fail to find com/github/felHR85/UsbSerial/7ad6c9f6/UsbSerial-7ad6c9f6.aar - correctly, because the actual artifact was: com/github/felHR85/UsbSerial/7ad6c9f6/UsbSerial-7ad6c9f6-release.aar
I managed to specify a classifier which seemed to move the error to the .jar.