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:
ap...@google.com <ap...@google.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> #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
Version used: 2.1.0
Devices/Android versions reproduced on: any device/version
When I define UUID as ids for my POJOs, and try to use @Relation, as result relation list is always empty.
Here is example:
object RoomTypeConverters {
@TypeConverter
@JvmStatic
fun uuidToData(uuid: UUID?): ByteArray = ...
@TypeConverter
@JvmStatic
fun dataToUUID(data: ByteArray?): UUID = ...
}
@Entity
data class Pet(
@ PrimaryKey
val uuid: UUID,
val userUuid: UUID,
val name: String
// other fields
)
data class UserNameAndAllPets(
val uuid: UUID,
val name: String,
@Relation(parentColumn = "uuid", entityColumn = "userUuid")
lateinit var pets: List<Pet>
)
@Dao
interface UserPetDao {
@Query("SELECT id, name from User")
fun loadUserAndPets(): List<UserNameAndAllPets>
}