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

JUnit is leaked on debug classpath #1414

Open
Raenar4k opened this issue Jun 5, 2024 · 0 comments
Open

JUnit is leaked on debug classpath #1414

Raenar4k opened this issue Jun 5, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Raenar4k
Copy link

Raenar4k commented Jun 5, 2024

Describe the bug
I had issues with running LeakCanary on our build because it detects JUnit on our debug classpath.
We setup all test dependencies properly - so we check where junit is coming from.

As you can see, one of dependencies of Wallet Connect is using junit and leaking it in classpath: com.github.komputing.kethereum

image

SDK Version

  • Client: Kotlin
  • Version 1.31.4

As a workaround for now i just remove junit from WC dependency:

    implementation(platform(libs.walletconnect.bom))
    implementation(libs.walletconnect.android) {
        exclude(group = "org.bouncycastle", module = "bcprov-jdk15on")
        exclude(group = "junit", module = "junit")
    }
    implementation(libs.walletconnect.sign) {
        exclude(group = "org.bouncycastle", module = "bcprov-jdk15on")
        exclude(group = "junit", module = "junit")
    }
@Raenar4k Raenar4k added the bug Something isn't working label Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant