You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked to make sure that this issue has not already been filed
Expected Behavior
The update to version 1.12.6 should have no errors
Current Behavior
This new update arrived via dependabot, and we see this error on each of our module that has unit tests:
> Could not resolve all files for configuration ':feature1:debugUnitTestRuntimeClasspath'.
> Could not find io.mockk:mockk-jvm:1.12.6.
- https://dl.google.com/dl/android/maven2/io/mockk/mockk-jvm/1.12.6/mockk-jvm-1.12.6.pom
- https://repo.maven.apache.org/maven2/io/mockk/mockk-jvm/1.12.6/mockk-jvm-1.12.6.pom
...
Failure Information (for bugs)
Steps to Reproduce
Have dependabot set up for your project
dependabot alerts to new MockK version
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
MockK version: 1.12.6
OS: MacOS 12.5.1
Kotlin version: 1.7.0
JDK version: 11
JUnit version: 5
Type of test: unit test
Stack trace
> Could not resolve all files for configuration ':feature1:debugUnitTestRuntimeClasspath'.
> Could not find io.mockk:mockk-jvm:1.12.6.
- https://dl.google.com/dl/android/maven2/io/mockk/mockk-jvm/1.12.6/mockk-jvm-1.12.6.pom
- https://repo.maven.apache.org/maven2/io/mockk/mockk-jvm/1.12.6/mockk-jvm-1.12.6.pom
...
Minimal reproducible code (the gist of this issue)
I'm reporting this issue for work, but I've also seen this issue with my personal app.
The text was updated successfully, but these errors were encountered:
alvindizon
changed the title
"Could not find io.mockk:mockk-jvm:1.12.6"
Encountered "Could not find io.mockk:mockk-jvm:1.12.6" when updating to 1.12.6
Aug 24, 2022
Expected Behavior
Current Behavior
Failure Information (for bugs)
Steps to Reproduce
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
Stack trace
Minimal reproducible code (the gist of this issue)
I'm reporting this issue for work, but I've also seen this issue with my personal app.
The text was updated successfully, but these errors were encountered: