Status Update
No update yet.
Comments
ni...@gmail.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:
da...@google.com
Will try to use the example provided by you to check if it fixes the issue.
da...@google.com
da...@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")
}
ap...@google.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"
da...@google.com
pr...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.room:room-runtime:2.7.0-alpha12androidx.room:room-runtime-android:2.7.0-alpha12androidx.room:room-runtime-iosarm64:2.7.0-alpha12androidx.room:room-runtime-iossimulatorarm64:2.7.0-alpha12androidx.room:room-runtime-iosx64:2.7.0-alpha12androidx.room:room-runtime-jvm:2.7.0-alpha12androidx.room:room-runtime-linuxarm64:2.7.0-alpha12androidx.room:room-runtime-linuxx64:2.7.0-alpha12androidx.room:room-runtime-macosarm64:2.7.0-alpha12androidx.room:room-runtime-macosx64:2.7.0-alpha12
Description
Component used: Room Version used: 2.2.6 Devices/Android versions reproduced on: Samsung Galaxy 8(Android 8.0/9.0) Samsung Galaxy 9(Android 8.0/9.0)
InvalidationTrackeruses in memory temp table( "CREATE TEMP TABLE ....") to notify about changes in tables; Declaring temp table for sqlite in WAL mode on some Samsung devices results inSQLiteConnectionPool.mMaxConnectionPoolSizebeing set to 1 (although, It should be at least 2 in WAL mode)So accessing to database in multiple threads cause to lock of threads. See logs:
SQLiteConnectionPool: The connection pool for database '<name of database>' has been unable to grant a connection to thread with flags 0x5 for 30.0010004 seconds. Connections: 0 active, 1 idle, 0 available