Why does `kotlin.native.cacheKind=none` is require...

# compose-ios

[SrSouza]

Why does kotlin.native.cacheKind=none is required for Compose iOS projects? What is the currently limitations and should we expect to be able to use any type of compilation caching in Compose iOS?

[xxfast]

there's a few different issues that has this workaround

[xxfast]

this seem to happen consistently when you switch target device on xcode, not sure why though

[Oleksandr Karpovich [JB]]

It seems that cache stored the symbols before compose made its transformations (that's the conclusion from the error messages: it tried to find a symbol that was transformed by compose, but cache? doesn't contain it).
Therefore it can't work with cache for now.
We'll try to fix this, but no timeline can be promised for now.