Fixed
Status Update
No update yet.
Comments
su...@google.com
that is weird. might be a studio issue, can you share the output of gradle? (the output from command line)
ro...@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.
su...@google.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 ?
ro...@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"`.
su...@google.com
so you are probably hitting
But in terms of why the error is not populating, i'm still baffled :/. The sample in
Is it possible for you to create a sample project that reproduces the error?
But in terms of why the error is not populating, i'm still baffled :/. The sample in
Is it possible for you to create a sample project that reproduces the error?
su...@google.com
Sure thing. I've created a super simple test project where the error output is the same.
Again, latest Android Studio latest stable release (3.0.1) on Mac OSX 10.13.3, embedded JDK.
Again, latest Android Studio latest stable release (3.0.1) on Mac OSX 10.13.3, embedded JDK.
Description
Version used: alpha01
WorkManager exposes method for cancellation of work. However, I currently don't see how this could be used if the work has already started.
Arguably, being able to cancel an ongoing work is very basic and must have functionality. Not being able to do so will render the entire framework unusable in many scenarios. It can also negatively impact the end users (e.g. by consuming too much battery/bandwidth).
Cancellation mechanism should be given a very good thought. As a starting point for a discussion, I propose adding two methods to Worker:
1) protected final boolean isCancelled() - will return true if the work has been cancelled
2) protected void onCancelled() - will be called after WorkManager determines that a specific Worker needs to be cancelled. Default implementation will be no-op.