Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed to resolve mockito-kotlin dependency

See original GitHub issue

Hi! I have

Error:Failed to resolve: com.nhaarman:mockito-kotlin-kt1.1:1.5.+

in the version 1.32.

I think it’s because of 1.5.+ versioning.

Excluding the module and adding dependency with 1.5.0 solves the issue.

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:10 (5 by maintainers)

Top GitHub Comments

2reactions

Jeevuzcommented, Dec 22, 2017

Yep, now all is ok!

0reactions

MarkusAmshovecommented, Dec 22, 2017

Thanks for confirming 😃

Top Results From Across the Web

Error:Failed to resolve: org.mockito:mockito-core

Solution: Change the dependency version to 2.13.0 instead of 2.13.3, then it works fine. Lessons Learnt: Always check with mvnrepository, ...

Doesn't work for Android tests · Issue #200 · mockito ... - GitHub

I am using this lib successfully for unit tests, but when I try to use it for an instrumented Android test, I get...

Importing a Gradle project fails with an exception in the latest ...

I've disabled the kotlin plugin, but still see the error: exception during working with external ... Could not resolve all dependencies for configuration ......

Downgrading versions and excluding dependencies

Gradle resolves any dependency version conflicts by selecting the latest ... Then this would trigger a resolution error because A says it needs...

Unit Testing with Mockito on Kotlin Android Project with ...

the reason is when Mockito mocks an object normally it extends the requested class to create an instance, but all Kotlin classes are...