Issues while using iOS runtime with v1.2.0-rc01

[soywiz]

I have PR that is trying to integrate compose runtime with KorGE here: korlibs/korge#485

It works on JS, JVM, Android and K/N desktop. But fails on iOS with a strange error. I have tried 1.2.0-rc01 with Kotlin 1.7.10, and the same version with Kotlin 1.7.20 and disabling JS to get it working. In both cases it fails, but with different errors:

To try this:

With kotlin 1.7.10 & JS enabled:

git clone https://github.com/korlibs/korge.git
cd korge
git checkout a86ef85a2fa2d19d68b6d0e8c37d9991b226b922 # branch feature/compose
./gradlew :korge-sandbox:runIosDeviceDebug 

With kotlin 1.7.20 & JS disabled:

git clone https://github.com/korlibs/korge.git
cd korge
git checkout d2af1f0725201d5ffbd3ecc744113afe8e89eaba # branch feature/compose.js.disabled
./gradlew :korge-sandbox:runIosDeviceDebug 

It is possible to try other targets:

./gradlew :korge-sandbox:runJvm
./gradlew :korge-sandbox:runJs
./gradlew :korge-sandbox:runNativeDebug

[soywiz]

Related issues #2342 #2346

[dima-avdeev-jb]

Thanks, I will research!

[abueide]

am also getting this issue except with material3 on 1.7.20 with js disabled

e: Module "chiachat:ui" has a reference to symbol androidx.compose.material3/Text|-8693233731735978503[0]. Neither the module itself nor its dependencies contain such declaration.

[dima-avdeev-jb]

@abueide I think, this is another Issue.
For now we don't have material3 builds for Compose Multiplatform

[dima-avdeev-jb]

@soywiz
Can you please try Compose Multiplatform version 1.3.0-alpha01-dev849

and add to gradle.properties:
kotlin.native.cacheKind=none

[soywiz]

@dima-avdeev-jb same issue:

Check this PR: korlibs/korge-compose#2

[dima-avdeev-jb]

@soywiz Can you also please try to use Kotlin 1.7.10 for now

[dima-avdeev-jb]

Maybe relates with #2342 and #2346

[soywiz]

Hey @dima-avdeev-jb , I have tried to build 1.7.10 locally, and now I get the first error (one local declaration instead of remember):

[okushnikov]

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.