The list of "org.jetbrains.compose.runtime:runtime-saveable (org.jetbrains.compose.runtime:runtime-saveable-uikitsimarm64): 1.3.0" dependencies that may lead to conflicts:
1. "stdlib: 1.8.0" (was initially compiled with "stdlib: 1.6.20")
2. "org.jetbrains.kotlin.native.platform.CoreFoundation: 1.8.0" (was initially compiled with "org.jetbrains.kotlin.native.platform.CoreFoundation: 1.6.21")
3. "org.jetbrains.kotlin.native.platform.darwin: 1.8.0" (was initially compiled with "org.jetbrains.kotlin.native.platform.darwin: 1.6.21")
4. "org.jetbrains.kotlin.native.platform.posix: 1.8.0" (was initially compiled with "org.jetbrains.kotlin.native.platform.posix: 1.6.20")
5. "org.jetbrains.kotlinx:atomicfu (org.jetbrains.kotlinx:atomicfu-iossimulatorarm64): 0.17.3" (was initially compiled with "org.jetbrains.kotlinx:atomicfu (org.jetbrains.kotlinx:atomicfu-iossimulatorarm64): 0.17.2")
6. "org.jetbrains.kotlinx:kotlinx-coroutines-core (org.jetbrains.kotlinx:kotlinx-coroutines-core-iossimulatorarm64): 1.6.4" (was initially compiled with "org.jetbrains.kotlinx:kotlinx-coroutines-core (org.jetbrains.kotlinx:kotlinx-coroutines-core-iossimulatorarm64)")

any help with resolving this?

You have to disable caching

kotlin.native.cacheKind=none

in your gradle.properties

@Landry Norris that worked but now am getting:

Undefined symbols for architecture arm64

As of right now, Compose methods cannot be public when building a dynamic framework. This can be solved in one of two ways: make the composable methods internal, or set the framework to build statically.

or set the framework to build statically

how to do that?

Are you using cocoapods, or do you declare frameworks when setting up iOS targets?

tried both, cocoapods and other one

If any undefined symbols have MTL at the start, you’re probably not linking against Metal. Have you looked at the samples in the compose-jb repo?

I just copy pasted existing project, which works