Closed lxr-mwhite closed 1 year ago
Hi, Github issue with recent change. Looking into it. As a workaround, you can implement the .aar locally from your grade file. https://github.com/SAP/gigya-android-sdk/releases/tag/core-v6.2.0
Thank you very much for the quick reply. We are considering the workaround you suggested, but will continue to keep an eye on the GitHub issue for future releases.
@tal-mi We are planning on making the changes to manually add the .aar file to our project instead of relying on Jitpack. However I was wondering if you had any status update on the GitHub issue?
I noticed version 6.2.1 of the SDK appears to have succeeded so that might be another option for us to update to that version, unless you think the issue is not fully resolved yet and could occur again with 6.2.1?
It might not be possible right now, but looking for some sort of ETA before we go ahead and manually include the .aar in our project.
Got a mixup in our git and we are sorting it out now. I would expect everything to be as it was by the end of today. Will update the issue accordingly.
Issue resolved. Sorry for the delay.
Thank you! I was waiting to verify, but I have seen a few successful builds on our CI agents since you've posted your comment.
I am good to close this issue.
As a note. Jitpack is being a real pain lately so I will be looking into progressing our builds to maven central as well as soon as I can. Will be posted
Hello,
Our project started having this issue 2-3 days ago (May 23, 2023) during the build process of our Android app. We have been using version 6.2.0 since February 27, 2023. Never had an issue with the build.
Our
build.gradle
file contains the following dependency:implementation 'com.github.SAP.gigya-android-sdk:sdk-core:core-v6.2.0'
Thank you for any help you can provide!