has anyone run into `Duplicate JVM class name` iss...
# multiplatform
b
has anyone run into
Duplicate JVM class name
issues working with `expect`/`actual`?
p
Got a gist to demonstrate?
b
i don't know what's causing the issue yet 😕
Figured it out: i had a
typealias
in a file in
commonMain
, which was otherwise only filled with
expect
declarations. This cause it to generate kt class for that file, when it otherwise wouldn't have
p
👍
r
Yeah,
*Kt
classes cause this. Had to switch to
*Jvm.kt
files for platform sourcesets, as I saw kotlinx libraries are doing similar thing.
☝️ 1
r
r
Oh cool, thanks! As KT-19507 is closed, I guess
@JvmName
+
@JvmMultifileClass
should also work?
👍 1
d
Exactly what @russhwolf said. Try not to mix
expect
and regular declarations in the same file is my approach.