If you want to try Compose 1.5.0-beta02 you should...
# compose-ios
d
If you want to try Compose 1.5.0-beta02 you should do the following with your project: • Update Compose version to
1.5.0-beta02
, 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
👌 10
m
Can we remove this line as well?
kotlin.native.cacheKind=none
🐕 3
d
Yes, you can remove since 1.5.0-beta02
kotlin.native.cacheKind=none
K 3
Also you need Kotlin 1.9.0
👌 1
m
I'll give it a try, thanks!
t
I'm seeing a lot of warnings after updating. Is this a known issue?
Copy code
warning: (arm64)  could not find object file symbol for symbol _kfun:kotlinx.serialization.json.internal.AbstractJsonTreeEncoder.$beginStructure$lambda$0$FUNCTION_REFERENCE$1.<init>#internal
warning: (arm64)  could not find object file symbol for symbol _kfun:kotlinx.serialization.json.internal.AbstractJsonTreeEncoder.$beginStructure$lambda$0$FUNCTION_REFERENCE$1.$<bridge-UNNN>invoke(kotlinx.serialization.json.JsonElement){}#internal
warning: (arm64)  could not find object file symbol for symbol _kfun:kotlinx.serialization.json.internal.<get-requiresTopLevelTag>#internal
warning: (arm64)  could not find object file symbol for symbol _kfun:kotlinx.serialization.json.internal.JsonPrimitiveEncoder.<init>#internal
warning: (arm64)  could not find object file symbol for symbol _kfun:kotlinx.serialization.json.internal.JsonPrimitiveEncoder.<get-content>#internal
warning: (arm64)  could not find object file symbol for symbol _kfun:kotlinx.serialization.json.internal.JsonPrimitiveEncoder.<set-content>#internal
warning: (arm64)  could not find object file symbol for symbol _kfun:kotlinx.serialization.json.internal.JsonPrimitiveEncoder.putElement#internal
These warnings are pretty annoying because they get logged for about 3 minutes straight before the compilation completes. This wasn't happening before I did the final changes as suggested for moving to compose 1.5.0-beta02. Anybody else seeing them?
s
@Trey I've tried
1.5.0-rc01
has been fixed.
👍 3