Checkout SDK includes the babylon dependency v0.3.0 which is old and the app crashed

[Martha Katsiki]

the checkout sdk version I use is implementation("com.checkout:checkout-sdk-3ds-android:2.0.1-testonly")

Here https://github.com/appmattus/certificatetransparency, the version I found is 1.0.0

When I try to build the app I get the following error:

• What went wrong:
  Execution failed for task ':app:checkUatAppNameDebugDuplicateClasses'.

Could not resolve all files for configuration ':app:uatAppNameDebugRuntimeClasspath'.
Could not find com.babylon.certificatetransparency:certificatetransparency-android:0.3.0.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/babylon/certificatetransparency/certificatetransparency-android/0.3.0/certificatetransparency-android-0.3.0.pom
- https://repo.maven.apache.org/maven2/com/babylon/certificatetransparency/certificatetransparency-android/0.3.0/certificatetransparency-android-0.3.0.pom
- file:/Users/n15757/newday-creditcard-android/m2/com/babylon/certificatetransparency/certificatetransparency-android/0.3.0/certificatetransparency-android-0.3.0.pom
- https://jitpack.io/com/babylon/certificatetransparency/certificatetransparency-android/0.3.0/certificatetransparency-android-0.3.0.pom
- https://salesforce-marketingcloud.github.io/MarketingCloudSDK-Android/repository/com/babylon/certificatetransparency/certificatetransparency-android/0.3.0/certificatetransparency-android-0.3.0.pom
- https://maven.pkg.github.com/checkout/checkout-3ds-sdk-android/com/babylon/certificatetransparency/certificatetransparency-android/0.3.0/certificatetransparency-android-0.3.0.pom
- file:/Users/n15757/newday-creditcard-android/app/libs/certificatetransparency-android-0.3.0.jar
- file:/Users/n15757/newday-creditcard-android/app/libs/certificatetransparency-android.jar
Required by:
project :app > com.checkout:checkout-sdk-3ds-android:2.0.1-testonly

[Shavinda Rabichandran]

Hi @MarthaKat15

Thank you for highlighting this issue. The issue is caused by one of the dependencies packages being renamed.

The dependency that is used by the current test release of the SDK is available in jcenter. So as an interim solution, you could make sure that the jcenter repository is enabled/configured for your project by updating the project level gradle file as follows;

allprojects {
    repositories {
        google()
        mavenCentral()
        jcenter()  // Add this line temporarily
    }
}

The next scheduled release of the SDK will be updated to use the new dependency details used in mavenCentral and will not require the jcenter() repository.

I will leave this issue open until the next release is made available.
Please let me know if you have any further issues.

[Martha Katsiki]

Hello,

this solution solved the issue. Thank you.

[Martha Katsiki]

@shavinda-rabichandran-cko any chance of this bug to be fixed, do we have the new SDK version soon?
Because the jcenter() repository is now deprecated in AS.

[Shavinda Rabichandran]

@MarthaKat15 We are planning to release a new build imminently (in process of going through validation).

The new build will remove the requirements to have the jcenter repository, however we will not be moving the certificatetransparency dependency to version 1.0.0 for now as this requires significant testing and evaluation, thus a much longer lead time.

I don't expect this to be a problem for you, but if you foresee any issues please let me know.

[Shavinda Rabichandran]

This issue has been resolved in the latest release 2.0.2 which is now available.

@MarthaKat15 Please let me know if you need any further assistance or you are encountering the issue after the upgrade.

[Martha Katsiki]

Thank you. I run the new version and it works well