-
Notifications
You must be signed in to change notification settings - Fork 601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6.1.0 can't be accessed from Jitpack anymore #375
Comments
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. |
Switching back from 6.1.0 to version 6.0.6 worked for me. |
@ChaseGuru Hey, you can try below custom implementation, it works on my side.
|
On the same principle i created a MR to update the dependencies and build successfully on jitpack. MR: #377
|
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. |
This is the workaround I did originally to get my deploy out. |
…Pack artifact error.
thanks this worked perfectly |
Yeah, there's a lot of great work arounds, and I've got it working. I'm using a flutter package, and someone made a different workaround in a fork of that which is what I'm currently using. My favorite fix probably is #377 - since it upgrades stuff and doesn't require changes to how the library is imported (if merged into this repo nobody would need to migrate their dependency declaration). |
The fork I'm using was this fork: Which is actually using the fix you suggested, as it was written by hwh97 who also made the initial suggestion. Though as mentioned, I'd probably prefer using #377's fork just because it upgrades stuff and seems like the best long term solution. |
My latest commit '0f16336a4e' fixed the build issue related to aar naming. Seems that 'archivesBaseName' screwed things. PR #377
|
On my flutter project I stil get this * What went wrong:
BUILD FAILED in 32s and my app/build.gradle look like this implementation('com.github.felHR85:UsbSerial:7ad6c9f6') { |
Missing debug aar |
As per your solution, If I put the .aar in local directly then while building the application got error Direct local .aar file dependencies are not supported when building an AAR |
Fixed with |
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.
The text was updated successfully, but these errors were encountered: