If you want to try Compose 1.5.0-beta01 you should...
# compose-ios
d
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
👍🏻 1
👍 8
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.
m
Is setting cacheKind=none in gradle.properties still required for compose iOS ? Because it's making the build slower
d
I will check your question
thank you color 2
You still need to set
cacheKind=none
in gradle.properties. But, we are thinking how to solve this problem
👍 1
m
Ok thanks!
c
d
As I see this blog post is fine in terms of performance
But, I added a comment to describe it on blog post
c
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 😅
thanks Dima!
d
Done:
😍 1
m
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?