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

Requires: com.linkedin.dexmaker:dexmaker or MockK could not self-attach on E2E test #10

Open
Arturo785 opened this issue Apr 5, 2023 · 0 comments

Comments

@Arturo785
Copy link

The first issue was that the current version of mockk private const val mockkVersion = "1.10.0"
was throwing this error when running the E2E Test which was solved using a newer version of mockk as stated in here

Requires: com.linkedin.dexmaker:dexmaker

mockk/mockk#1000
Mine selected version was
private const val mockkVersion = "1.11.0"

Then after this the next error was this one
_

java.lang.ExceptionInInitializerError
at com.example.calorietracker.TrackerOverviewE2E.setUp(TrackerOverviewE2E.kt:319)
... 56 trimmed
Caused by: io.mockk.proxy.MockKAgentException: MockK could not self-attach a jvmti agent to the current VM. This feature is required for inline mocking.
This error occured due to an I/O error during the creation of this agent: java.io.IOException: Unable to dlopen libmockkjvmtiagent.so: dlopen failed: library "libmockkjvmtiagent.so" not found

Potentially, the current VM does not support the jvmti API correctly

_

which was fixed doing this as stated in here
mockk/mockk#297

mine was fixed adding this to the app module dependency only

    implementation("com.github.wseemann:FFmpegMediaMetadataRetriever-core:1.0.15")
    implementation("com.github.wseemann:FFmpegMediaMetadataRetriever-native:1.0.15")

feel free to add it to buildSrc as a more clean approach

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant