Skip to content

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

@Arturo785

Description

@Arturo785

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions