If you want to try Compose 1.5.0-beta01 you should do the following with your project: - Update Comp...

# compose-ios

[Dima Avdeev]

If you want to try Compose 1.5.0-beta01 you should do the following with your project:
• Update Compose version to 1.5.0-beta01 , Kotlin version to 1.9.0
• Remove line with resources https://github.com/JetBrains/compose-multiplatform-ios-android-template/blob/c20faa099552dac7bcc242c72fe49e1f260177e9/shared/build.gradle.kts#L25
• And run command ./gradlew podInstall once

[Dima Avdeev]

Now resources packed with another way. We pack resources with our Gradle plugin instead of cocoapods.
So, now it is easier migrate to Regulare Xcode framework.

[mohamed rejeb]

Is setting cacheKind=none in gradle.properties still required for compose iOS ? Because it's making the build slower

[Dima Avdeev]

I will check your question

[Dima Avdeev]

You still need to set cacheKind=none in gradle.properties. But, we are thinking how to solve this problem

[mohamed rejeb]

Ok thanks!

[Colton Idle]

should we update https://blog.jetbrains.com/kotlin/2023/08/help-improve-compose-multiplatform-apps-performance/ with those instructions @Dima Avdeev?

[Dima Avdeev]

As I see this blog post is fine in terms of performance

[Dima Avdeev]

But, I added a comment to describe it on blog post

[Colton Idle]

yeah. i was just making a point that the blog post includes instructions on how to update. but the instructions in slack had more detail 😅

[Colton Idle]

thanks Dima!

[Dima Avdeev]

Done:

[Marc Dietrichstein]

We are using org.jetbrains.kotlin.gradle.plugin.mpp.apple.XCFramework instead of the CocoaPods Plugin to build our framework. This way we do get a MissingResourceException when we attempt to access a resource on iOS. Is it possible that this approach is not supported with Kotlin 1.9.0 and Compose 1.5.0-beta01? Or to put it differently: Is the CocoaPods plugin necessary in order to package resources correctly?