Skip to content
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

CI Build: Could not resolve cardinalmobilesdk: Received status code 403 from server: Forbidden #325

Closed
ersen-lw opened this issue Jan 12, 2022 · 15 comments

Comments

@ersen-lw
Copy link

ersen-lw commented Jan 12, 2022

General information

  • SDK/Library version: 6.0.0
  • Environment: N/A
  • Android Version and Device: N/A

Issue description

This issue occurs when our CI builds our application. Locally, do not have this issue because I guess the dependency is cached.
The repository that hosts the cardinalcommerce dependency appears to be unstable lately.

  • Occurred a few times last week
  • Yesterday was fine
  • Today encounter the same issue

This is the error:

* What went wrong:
Execution failed for task ':app:dataBindingMergeDependencyArtifactsAlpha'.
> Could not resolve all files for configuration ':app:alphaRuntimeClasspath'.
   > Could not resolve org.jfrog.cardinalcommerce.gradle:cardinalmobilesdk:2.2.5-4.
     Required by:
         project :app > com.braintreepayments.api:drop-in:6.0.0 > com.braintreepayments.api:three-d-secure:4.7.0
      > Could not resolve org.jfrog.cardinalcommerce.gradle:cardinalmobilesdk:2.2.5-4.
         > Could not get resource 'https://cardinalcommerceprod.jfrog.io/artifactory/android/org/jfrog/cardinalcommerce/gradle/cardinalmobilesdk/2.2.5-4/cardinalmobilesdk-2.2.5-4.pom'.
            > Could not GET 'https://cardinalcommerceprod.jfrog.io/artifactory/android/org/jfrog/cardinalcommerce/gradle/cardinalmobilesdk/2.2.5-4/cardinalmobilesdk-2.2.5-4.pom'. Received status code 403 from server: Forbidden

I double checked the credentials here https://developer.paypal.com/braintree/docs/guides/3d-secure/migration/android/v4 which is correct.

This is a snippet from the build.gradle file from the app module.

repositories {
    google()
    mavenCentral()
    maven {
        url "https://cardinalcommerceprod.jfrog.io/artifactory/android"
        credentials {
            username 'braintree_team_sdk'
            password 'AKCp8jQcoDy2hxSWhDAUQKXLDPDx6NYRkqrgFLRc3qDrayg6rrCbJpsKKyMwaykVL8FWusJpp'
        }
    }
}


dependencies {
    implementation "com.braintreepayments.api:drop-in:6.0.0"
}
@ersen-lw ersen-lw changed the title Could not resolve cardinalmobilesdk: Received status code 403 from server: Forbidden CI Build: Could not resolve cardinalmobilesdk: Received status code 403 from server: Forbidden Jan 12, 2022
@sarahkoop
Copy link
Contributor

Thank you for reporting this issue. Those credentials are correct, so it does seem like this is an intermittent failure from the hosting repository. We will report this issue to Cardinal. In the meantime, if you (and anyone else experiencing this issue) could continue to comment here when you are experiencing problems accessing the Cardinal Mobile SDK, that would be helpful to determine how widespread the issue is.

@jplukarski
Copy link
Contributor

@ersen-lw, Cardinal is wondering if you are still experiencing these issues and, if so, what the frequency is.

@ersen-lw
Copy link
Author

ersen-lw commented Mar 8, 2022

Apologies for the late reply. Haven't encountered this issue in a long time now. Most likely was just server instability at the time. I will close this.

@ersen-lw ersen-lw closed this as completed Mar 8, 2022
@JHFarrant
Copy link

JHFarrant commented Jul 13, 2022

@jplukarski I am experiencing the issue at the moment, could it be that the user is being temporarily locked?
Screenshot 2022-07-13 at 10 42 54

@sshropshire
Copy link
Contributor

@JHFarrant I don't believe those are login credentials. They should be used only for authentication with Cardinal's Maven repository via Gradle.

@matejsemancik
Copy link

Hello, I've been experiencing the same issue since today. I had dependency cached locally since last week, but today ran on CI and this issue popped up on latest SDK version (6.14.0).

@matejsemancik
Copy link

Seemed to be intermittent after all. The access to repository works again.

@ersen-lw ersen-lw reopened this Mar 6, 2024
@ersen-lw
Copy link
Author

ersen-lw commented Mar 6, 2024

From last week, my CI builds have been failing with 403 from the cardinalcommerceprod.jfrog repo.
Can this be communicated to them?

> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not resolve org.jfrog.cardinalcommerce.gradle:cardinalmobilesdk:2.2.7-5.
     Required by:
         project :app > com.braintreepayments.api:drop-in:6.13.0 > com.braintreepayments.api:three-d-secure:4.38.2
      > Could not resolve org.jfrog.cardinalcommerce.gradle:cardinalmobilesdk:2.2.7-5.
         > Could not get resource 'https://cardinalcommerceprod.jfrog.io/artifactory/android/org/jfrog/cardinalcommerce/gradle/cardinalmobilesdk/2.2.7-5/cardinalmobilesdk-2.2.7-5.pom'.
            > Could not GET 'https://cardinalcommerceprod.jfrog.io/artifactory/android/org/jfrog/cardinalcommerce/gradle/cardinalmobilesdk/2.2.7-5/cardinalmobilesdk-2.2.7-5.pom'. Received status code 403 from server: 

@ersen-lw
Copy link
Author

ersen-lw commented Apr 3, 2024

image

@aminezebdi
Copy link

Hello, we are currently experiencing the same issue today. Our CI builds are failing with the same error (status 403).

@mtrakal
Copy link

mtrakal commented Apr 4, 2024

Hmm, still happen (but I comment it in different project): paypal/android-checkout-sdk#239 (comment)

@desxz
Copy link

desxz commented Apr 4, 2024

Hello folks, we are also getting same issue today on our CI. Our drop-in sdk version is 5.4.2 and cardinal version is 2.2.7-5
Also, I can swear that I authenticated to the jfrog website with the same credentials to update the cardinal package in the past months and checked the versions.

Execution failed for task ':app:dataBindingMergeDependencyArtifactsDebug'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not download cardinalmobilesdk-2.2.7-5.aar (org.jfrog.cardinalcommerce.gradle:cardinalmobilesdk:2.2.7-5)
      > Could not get resource 'https://cardinalcommerceprod.jfrog.io/artifactory/android/org/jfrog/cardinalcommerce/gradle/cardinalmobilesdk/2.2.7-5/cardinalmobilesdk-2.2.7-5.aar'.
         > Could not GET 'https://cardinalcommerceprod.jfrog.io/artifactory/android/org/jfrog/cardinalcommerce/gradle/cardinalmobilesdk/2.2.7-5/cardinalmobilesdk-2.2.7-5.aar'. Received status code 403 from server: 

@desxz
Copy link

desxz commented Apr 5, 2024

It fixed on our CI

@sarahkoop
Copy link
Contributor

Closing this issue as it has been resolved by JFrog and Cardinal - please re-open if you continue to experience this issue!

@ersen-lw
Copy link
Author

Hi @sarahkoop

We started to see this issue again today

> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not resolve org.jfrog.cardinalcommerce.gradle:cardinalmobilesdk:2.2.7-5.
     Required by:
         project :app > com.braintreepayments.api:drop-in:6.15.0 > com.braintreepayments.api:three-d-secure:4.41.0
      > Could not resolve org.jfrog.cardinalcommerce.gradle:cardinalmobilesdk:2.2.7-5.
         > Could not get resource 'https://cardinalcommerceprod.jfrog.io/artifactory/android/org/jfrog/cardinalcommerce/gradle/cardinalmobilesdk/2.2.7-5/cardinalmobilesdk-2.2.7-5.pom'.
            > Could not GET 'https://cardinalcommerceprod.jfrog.io/artifactory/android/org/jfrog/cardinalcommerce/gradle/cardinalmobilesdk/2.2.7-5/cardinalmobilesdk-2.2.7-5.pom'. Received status code 403 from server: 
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants