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"

re comment#5: Can you elaborate on what you mean? Can you share some sample code?

Hi, this still seems to be a problem in 2.7.0-alpha11. However, I do not use @RawQuery in my code. I have a custom class that makes use of @Embedded an @Relation which seems to use this under the hood since I receive this honestly meaningless error message The @Database class must be annotated with @ConstructedBy since the source is targeting non-Android platforms..

I only found out about this being related to the missing implementation of @RawQuery on other platforms than Android by running a search with parts of it in quotation marks as the only reference I could find was a single commit in a Git-Repository: https://android.googlesource.com/platform/frameworks/support/+/bd5954b4a4b29fb8093519485c8c4a62c4a5ece5%5E1..bd5954b4a4b29fb8093519485c8c4a62c4a5ece5/ (just search for the first few words of the error message).

This is a breaking problem for me at the moment since it prevents me from building APKs. Running the app on an emulator works just fine. This issue is marked as fixed and the fix got merged but as I said earlier, it seems to still be there. Is there anything that need to be changed in the code? If the fix isn't rolled out in a new room-Version, when will the time be? Thanks in advance!

re comment#7: Your issue does not seem related to @RawQuery APIs, can you please file a new bug?

If you are having issue with Room's KMP setup see the following comment for things to checkout: https://issuetracker.google.com/342905180#comment21

I have to admit I don't have any clue how I fixed the problem, but it's now fixed :D

comment#8 I know that it is not directly related to the @RawQuery-API but the error I received was.