Could not determine artifacts for com.github.Tap-Payments:TapCardValidator-Android:2.1.0

[peymancyb]

Hi,
this error happens on version 3.2.5

> Could not resolve all dependencies for configuration ':app:demoReleaseRuntimeClasspath'.
   > Could not determine artifacts for com.github.Tap-Payments:TapCardValidator-Android:2.1.0
      > Could not get resource 'https://jitpack.io/com/github/Tap-Payments/TapCardValidator-Android/2.1.0/TapCardValidator-Android-2.1.0.aar'.
         > Could not HEAD 'https://jitpack.io/com/github/Tap-Payments/TapCardValidator-Android/2.1.0/TapCardValidator-Android-2.1.0.aar'. Received status code 401 from server: Unauthorized

[HaithamSheshtawy]

I integrated it with empty project and it works fine, so could u please tell me
what version you are using for build gradle? is it com.android.tools.build:gradle:3.5.0?

[peymancyb]

@HaithamSheshtawy thanks for the response, yes it is com.android.tools.build:gradle:3.5.0

[HaithamSheshtawy]

can you share log with me and also your gradle
h.sheshtawy@tap.company

[peymancyb]

Thank you @HaithamSheshtawy, I have already shared it to the mentioned email address.

[mirland]

I'm facing exactly the same issue in the goSellSDK-Android library (version 2.4.6).

[HaithamSheshtawy]

now it's public could u please test

[HaithamSheshtawy]

Our jitPack artifact report for the latest release:

[peymancyb]

@HaithamSheshtawy Thanks for the update, yes now it's fixed!

[HaithamSheshtawy]

Great

…

On Thu, Nov 7, 2019 at 11:00 AM Peyman ***@***.***> wrote: @HaithamSheshtawy <https://github.com/HaithamSheshtawy> Thanks for the update, yes now it's fixed! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=AK6JZJVJI2EZZB4YSQNOTSTQSPDJDA5CNFSM4JIS3AY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDLRPYY#issuecomment-550967267>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK6JZJU2G4SHIPPGPZK3QB3QSPDJDANCNFSM4JIS3AYQ> .

[HaithamSheshtawy]

@HaithamSheshtawy Thanks for the update, yes now it's fixed!

can u please close the issue if it's fixed

[peymancyb]

Yes sure! thanks.