Status Update
No update yet.
Comments
to...@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:
xm...@gmail.com
Will try to use the example provided by you to check if it fixes the issue.
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")
}
xm...@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"
ap...@google.com
Branch: androidx-master-dev
commit 302a9bd0131103b3c4b380089bd42788111554ec
Author: Daniel Santiago Rivera <danysantiago@google.com>
Date: Thu Feb 20 11:24:57 2020
Use tracker lookup table names when creating multi-instance observer.
When creating the multi-instance invalidation tracker observer use the
table lookup keys which correspond to the available table names to
observe and not the names in the internal table names array since those
are mapped to the shadow tables and in the case of an FTS table to a
non-visible table such as Foo_content.
Bug: 148969394
Test: MultiInstanceInvalidationTest
Change-Id: Ief0a906ccd6a87d285035d65f6b4bd87837006f6
M room/integration-tests/testapp/src/androidTest/java/androidx/room/integration/testapp/test/MultiInstanceInvalidationTest.java
A room/integration-tests/testapp/src/main/java/androidx/room/integration/testapp/database/Description.java
M room/integration-tests/testapp/src/main/java/androidx/room/integration/testapp/database/Product.java
M room/integration-tests/testapp/src/main/java/androidx/room/integration/testapp/database/ProductDao.java
M room/integration-tests/testapp/src/main/java/androidx/room/integration/testapp/database/SampleDatabase.java
M room/runtime/src/main/java/androidx/room/InvalidationTracker.java
M room/runtime/src/main/java/androidx/room/MultiInstanceInvalidationClient.java
da...@google.com
xm...@gmail.com
an...@google.com
to...@gmail.com
da...@google.com
to...@gmail.com
xm...@gmail.com
yb...@google.com
Yes, you can use the build snapshots
Note that this is usually not recommended but at this point in time, Room master is fairly stable and has only bugfixes from the previous release.
Description
@Fts4(tokenizer = FtsOptions.TOKENIZER_UNICODE61)
class WorldFts(
var word: String
)
java.lang.IllegalArgumentException: There is no table with name word_fts_content
at androidx.room.InvalidationTracker.addObserver(InvalidationTracker.java:266)
at androidx.room.MultiInstanceInvalidationClient$3.run(MultiInstanceInvalidationClient.java:124)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
It happens when use room Fts4 annotation with enableMultiInstanceInvalidation in room database.