Fixed
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:
se...@gmail.com <se...@gmail.com> #3
Yes this does seem like a KSP issue however it only starts happening when room is added to the project. As the template project compiles just fine.
Will try to use the example provided by you to check if it fixes the issue.
Will try to use the example provided by you to check if it fixes the issue.
da...@google.com <da...@google.com>
ap...@google.com <ap...@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")
}
Description
Component used: Room
Version used: 2.3.0-alpha04
Devices/Android versions reproduced on: Emulator API 26 with google services
Case 1: Consider Base DAO class
And class
It is expected that the generated implementation code will have 3 Update methods with corresponding conflict strategies.
What is actually generated:
Actual - all update methods are using the same adapter with ABORT.
Case 2: Change very first update strategy to IGNORE in BaseDao
And now adapter becomes:
Case 3: Use case 2 and add a new method to ComanyDao:
then update implementation becomes