Status Update
Comments
ya...@google.com <ya...@google.com>
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:
ap...@google.com <ap...@google.com> #3
Will try to use the example provided by you to check if it fixes the issue.
da...@google.com <da...@google.com>
ys...@gmail.com <ys...@gmail.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")
}
nn...@gmail.com <nn...@gmail.com> #5
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"
Description
@Entity
data class User(
@PrimaryKey id: Long,
name: String,
email: String?
)
data class UserName(id: Long, name: String)
data class UserEmail(id: Long, email: String)
@Dao
interface UserDao {
@Insert(entity = User::class)
insertWithoutEmail(userName: UserName)
@Update(entities = User::class)
updateEmail(userEmail: UserEmail)
}
- The @Insert example above is a bit silly, but it makes sense when you want to leave out columns with default values (
- We probably need a better API to support insertion/update of multiple entities/pojos.