Status Update
No update yet.
Comments
yb...@google.com
fl...@google.com
ap...@google.com
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:
fl...@google.com
mi...@gmail.com
Will try to use the example provided by you to check if it fixes the issue.
fe...@gmail.com
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")
}
fe...@gmail.com
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
Version used: 1.1.0
Devices/Android versions reproduced on: All
When we are working with Room database that contains predefined data, we can populate these predefined data when first creation of the database via Callback#onCreate(SupportSQLiteDatabase). If that project decided to fallback to destructive migration, all the predefined data will be delete during the migration and there is no way to notify if that happens so we can insert those predefined data.
My suggestion would be adding a new callback method e.g. onDestructiveMigrate(SupportSQLiteDatabase). Then notify the callback once migrated by destruction.