Status Update
No update yet.
Comments
cl...@google.com
cl...@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:
ap...@google.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")
}
jo...@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"
pr...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.room:room-paging:2.6.1
Description
Technical Details
This sample app showcases how there is no error propagation available when using default PagingSource in queries. The sample app has a text field that filters a list of animals. The MATCH statement is used to throw an Exception but there may be other ways to do this as well.
Steps to reproduce:
Under the covers, the default implementation of PagingSource in DAO queries is LimitOffsetPagingSource.
In this particular case, we have options to mitigate this:
In lieu of an actual fix, there should probably be documentation that acknowledges and warns about situations using the default PagingSource, particularly in instances where the MATCH statement is used with user input since this is a common use case with FTS4 entities that requires special care.
There are a few StackOverflow issues that mention this issue, both reported years ago, but I could not find any bug reports: