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

Fix: Chucker dependency cannot be resolved when running verify newproject script #485

Closed
ryan-conway opened this issue Jul 12, 2023 · 0 comments · Fixed by #486 or #487
Closed

Fix: Chucker dependency cannot be resolved when running verify newproject script #485

ryan-conway opened this issue Jul 12, 2023 · 0 comments · Fixed by #486 or #487

Comments

@ryan-conway
Copy link
Collaborator

ryan-conway commented Jul 12, 2023

Issue

CI fails when running the verify newproject script.

* What went wrong:
Execution failed for task ':app:dataBindingMergeDependencyArtifactsProductionDebug'.
> Could not resolve all files for configuration ':app:productionDebugCompileClasspath'.
   > Failed to transform library-3.5.2.aar (com.github.chuckerteam.chucker:library:3.5.2) to match attributes {artifactType=android-databinding, org.gradle.category=library, org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.usage=java-api}.
      > Could not find library-3.5.2.jar (com.github.chuckerteam.chucker:library:3.5.2).
        Searched in the following locations:
            https://jitpack.io/com/github/chuckerteam/chucker/library/3.5.2/library-3.5.2.aar
            https://jitpack.io/com/github/chuckerteam/chucker/library/3.5.2/library-3.5.2.jar

We should fetch Chucker from Maven instead of Jitpack to prevent this from occuring

The syntax we implemented to get maven (Jitpack) should be in Kotlin format:

repositories {
  maven { url = uri("https://www.jitpack.io" ) }
}

Ref: https://stackoverflow.com/a/66926254/11393626

Expected

CI should be able to execute the verify newproject script successfully

Steps to reproduce

  1. Open a PR
  2. Let CI run
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment