Fixed
Status Update
No update yet.
Comments
yb...@google.com
fl...@google.com
ap...@google.com
that is weird. might be a studio issue, can you share the output of gradle? (the output from command line)
fl...@google.com
mi...@gmail.com
Here it is, with --info.
Since the module is a mixed Java/Kotlin one, I have tried with both annotationProcessor and kapt.
The result is the same, no indication about the failure.
Since the module is a mixed Java/Kotlin one, I have tried with both annotationProcessor and kapt.
The result is the same, no indication about the failure.
fe...@gmail.com
that is so weird, we always report that error w/ a reference to the field:
context.checker.check(success, field.element, CANNOT_FIND_GETTER_FOR_FIELD)
can you share your build.gradle file? Which version of kotlin are you using?
Also, make sure you have kotlin-kapt plugin applied.
Also, I realized that you've put version 1.1.0-alpha5 which does not exist. Did you mean 1.1.0-alpha1 or 1.0.0-alpha5 ?
context.checker.check(success, field.element, CANNOT_FIND_GETTER_FOR_FIELD)
can you share your build.gradle file? Which version of kotlin are you using?
Also, make sure you have kotlin-kapt plugin applied.
Also, I realized that you've put version 1.1.0-alpha5 which does not exist. Did you mean 1.1.0-alpha1 or 1.0.0-alpha5 ?
fe...@gmail.com
Apologies, I meant to write 1.1.0-alpha1.
Worth mentioning that the @Database class and the @Entity are in two different library modules, one directly depending on the other.
Both modules are using Kotlin version 1.2.21, kotlin-apt and `kapt "android.arch.persistence.room:compiler:1.1.0-alpha1"`
and `implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.2.21"`.
Worth mentioning that the @Database class and the @Entity are in two different library modules, one directly depending on the other.
Both modules are using Kotlin version 1.2.21, kotlin-apt and `kapt "android.arch.persistence.room:compiler:1.1.0-alpha1"`
and `implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.2.21"`.
Description
Version used: 1.1.0
Devices/Android versions reproduced on: All
When we are working with Room database that contains predefined data, we can populate these predefined data when first creation of the database via Callback#onCreate(SupportSQLiteDatabase). If that project decided to fallback to destructive migration, all the predefined data will be delete during the migration and there is no way to notify if that happens so we can insert those predefined data.
My suggestion would be adding a new callback method e.g. onDestructiveMigrate(SupportSQLiteDatabase). Then notify the callback once migrated by destruction.