Status Update
Comments
da...@google.com <da...@google.com> #2
For Kotlin 2.0 and KSP 2.0 the Cannot change attributes of configuration ':composeApp:debugFrameworkIosX64' after it has been locked for mutation
really seems like a KSP issue. You should file a bug in their repository with a sample app if possible.
If you downgrade to Kotlin 1.9 then things 'should' work, there are example apps out there with such configuration, like the following one:
tn...@google.com <tn...@google.com> #3
Will try to use the example provided by you to check if it fixes the issue.
tn...@google.com <tn...@google.com> #4
Note that this issue happens when applying the Compose, KSP and Room Plugin together in Kotlin 2.0.x, the workaround for now is to not use the Room Gradle Plugin and instead specify the schema location vis KSP arguments:
// In the build.gradle
ksp {
arg("room.schemaLocation", "${projectDir}/schemas")
}
da...@google.com <da...@google.com> #5
Hi, I encountered a similar problem and was able to resolve it by updating the dependencies
room = "2.7.0-alpha08"
ksp = "2.0.20-1.0.25"
compose-plugin = "1.6.11"
kotlin = "2.0.20"
Description
Room recently moved some of its APIs and source from Java to Kotlin and int def enforcement seems to have been lost with the move.
Given the IntDef in Room OnConflictStrategy , wrong usage of it in Kotlin gives no warning:
the enforcement is also lost in Java sources:
However, if I make a new
@IntDef
along with an annotation in Java, the enforcement works fine.Let me know if you need more information!