Oleksandr Karpovich

the link you provided (https://luludevmuniz.github.io/Po11nt-site/) is 404. Could you please check that link is correct?

Do you have a reproducer for this issue? ___ There is a template when you create a new issue. Please follow it. Especially the "Steps to reproduce" part

Identified a change causing this behaviour: https://github.com/JetBrains/compose-multiplatform/pull/4604/files#diff-b723358a9cc467fc156c914c8767b75387ca863c0387a2e0850a44e4d1086f18R29 Workaround: - apply `kotlin("multiplatform")` instead of `kotlin("android")`, - rename the source set folder ("main" -> "androidMain") - and configure the target: ``` kotlin...

@eygraber The new CM libraries (runtime, ui, foundation, etc.) build is required (WiP). The new compiler version in your project is not enough.

@vickyleu Voyager library has to be updated to new Compose first. Then new Voyager version should be used in the projects.

Could be a custom build of Voyager perhaps? The stacktrace points to voyager. But the reproducer would indeed help investigate it.

@vickyleu you can try two options: 1) use kotlin 1.9.23 to compile the library/dependency 2) try to add these two parameters in gradle.properties: kotlin.native.cacheKind=none compose.kotlin.native.manageCacheKind=false

It seems like your project has a dependency on a library which depends on a newer skiko version, while your project depends on older skiko. Newer skiko doesn't have the...

Since you mentioned that you managed to make K/Wasm target work (here: https://github.com/JetBrains/compose-multiplatform/issues/4811), I close this issue.

Reproduced the on Desktop as well: - delay is not respected - while loop never stops It makes sense because `runComposeUiTest ` is implemented by SkikoComposeUiTest on all platforms except...