NPE crash onWorkFinished [116253486]

Fixed

Bug

Status Update

No update yet.

Description

ot...@gmail.com

created issue #1

Sep 21, 2018 03:28PM

Component used: WorkManager
Version used: 1.0.0-alpha09
Devices/Android versions reproduced on:
LG LGMS210

crash log

java.lang.NullPointerException: Attempt to invoke virtual method 'boolean androidx.work.o.a()' on a null object reference
at androidx.work.impl.WorkerWrapper.onWorkFinished(WorkerWrapper.java:260)
at androidx.work.impl.WorkerWrapper$1.run(WorkerWrapper.java:224)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)

don't have more information

Comments

ra...@google.com <ra...@google.com> Sep 22, 2018 05:15AM

Assigned to ra...@google.com.

su...@google.com <su...@google.com> Sep 24, 2018 08:24PM

Reassigned to su...@google.com.

ap...@google.com <ap...@google.com> #2Sep 25, 2018 04:35PM

Seems like it happens on API 21-22 too.

su...@google.com <su...@google.com> #3Sep 25, 2018 04:41PM

Marked as fixed.

This is expected. You are calling: enqueueUniquePeriodicWork() with an ExistingPeriodicWorkPolicy.REPLACE. This will cancel running work, and kick off new instances of all Workers.

https://github.com/rubensousa/WorkManagerKitkatBug/blob/master/app/src/main/java/com/github/rubensousa/workkitkatbug/MainActivity.kt#L24

ot...@gmail.com <ot...@gmail.com> #4Sep 25, 2018 04:43PM

I just ran the sample again and now the behaviour is different for some weird reason. I forgot to mention that I only used REPLACE to test this properly. Because it also happens with KEEP.

Issue 116253486