IssueTracker

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: https://github.com/realityexpander/KMP_Room/tree/main

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")
}

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"

Hey, thank you so much for the reproducible project. The legacy hash is based on CREATE statements and it looks like that our backwards compatibility logic missed a detail.

In Room 2.2.0 we updated the CREATE INDEX statement to also included IF NOT EXSIST. We remove the latter section when calculating the legacy hash, buuuut turns out that the previous CREATE INDEX statement had two spaces between the CREATE and INDEX words, while the updated statement along with the backward compatibility adjustment makes it have one, causing the hash to be different.

I'll try to fix this soon, might end up in a Room 2.2.3 release.