Closed IniongunIsaac closed 4 years ago
Best guess is that you probably have both the regular threetenbp dependency and the 'notzdb'-qualified dependency on your classpath? I would check the output of the dependencies
task and look for where threetenbp is coming from.
Unfortunately there's no answer that I can really give because it's not a problem with the library, but a misconfiguration of your project. Once you identify where the errant, non-'notzdb' version of the threetenbp is coming from, you can either exclude it or use a Gradle resolution strategy to replace it with the 'notzdb' version in which case Gradle will de-duplicate them.
If you use "testImplementation" or "androidTestImplementation" to implement a module that also has this dependency, you need to declare it as non-transitive dependency:
androidTestImplementation(project(":sharedTests")) { transitive = false }
This worked to me!
I came across this stacktrace when trying to write some android tests: