Fixed
Status Update
Comments
ra...@google.com <ra...@google.com>
ra...@google.com <ra...@google.com> #2
I guess technically, the ProGuard rule should be on androidx.work.NonBlockingWorker subclasses, but I'd also be okay with just not using reflection to access the Worker(Context, WorkerParamters) constructor and skipping the need for a ProGuard rule at all.
Description
android.arch.work:work-runtime-ktx:1.0.0-alpha06
Version used:
Theme used: N/A
Devices/Android versions reproduced on: All
- Relevant code to trigger the issue.
class SomeWorker: Worker() {
fun doWork() {
val input = inputData.getIntArray("key")
if( input == null || input.isEmpty() ) {
// work
}
}
}
there is a lint warning on "input == null" saying it is always false. This is because the return type is annotated with @NonNull. The javadoc and code clearly say/show that null can be returned.
The same holds true for getBooleanArray(String)
- A screenrecord or screenshots showing the issue (if UI related).
N/A