What changed? Surely it IS Kotlin, due to the coro...

# getting-started

[MarkRS]

What changed? Surely it IS Kotlin, due to the coroutines involvement! I've just started getting

Execution failed for task ':androidApp:mergeBasicReleasetestingJavaResource'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.MergeJavaResWorkAction
> 2 files found with path 'win32-x86-64/attach_hotspot_windows.dll' from inputs:
- /home/mark/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-debug/1.7.1/5299f4f5c0158ec6b7a2f1c11e2d5feb33c77e9f/kotlinx-coroutines-debug-1.7.1.jar
- /home/mark/.gradle/caches/modules-2/files-2.1/net.bytebuddy/byte-buddy-agent/1.10.9/cbbeffa557e6b1b4cbb181b0782436921c523699/byte-buddy-agent-1.10.9.jar

I've tried excluding both of those files (individually) with android packaging options, but I get the same complaint. I have no idea what changed that this suddenly became an option, I've only been working with Android tests recently, and this is an app build, as you can see.
How to get past this?

Again, this is a Kotlin issue, as explained here. Which means this is now solved.