Why workers in work manager still in ENQUEUED state?

Question

I'm creating OneTimeWorkRequest with NetworkType.CONNECTED constraint, but even though the device is connected to the internet, the request is still in ENQUEUED state

Constraints constraints = new Constraints.Builder().setRequiredNetworkType(NetworkType.CONNECTED).build();

OneTimeWorkRequest request = new OneTimeWorkRequest.Builder(SyncWorker.class)
            .setConstraints(constraints)
            .build();

WorkContinuation continuation = mWorkManager.beginUniqueWork("work",
                    ExistingWorkPolicy.KEEP, request);

continuation.enqueue();

Is your SyncWorker an inner class? https://stackoverflow.com/a/55515760/18202 — Mike Hall, Dec 14 '20 at 02:39
Did you find any solution? Some of my users are currently facing the same issues with some of their china phones like Tecno — Jayhymn, Mar 20 '23 at 20:49

score 0 · Answer 1 · answered Jul 03 '18 at 07:37

0

Try this?

Constraints constraints = new Constraints.Builder().setRequiredNetworkType(NetworkType.CONNECTED).build();

OneTimeWorkRequest request = new OneTimeWorkRequest.Builder(SyncWorker.class)
            .setConstraints(constraints)
            .build();

WorkManager.getInstance().enqueue(request);

answered Jul 03 '18 at 07:37

TomH

2,581
1
15
30

Have you debugged into your worker class to see if it is being executed? Is it possible it's not succeeding and therefore retrying itself? – TomH Jul 04 '18 at 09:01
facing the same issue with the beta03 release of the library. Worker used to be triggered but since yesterday its not triggered at all and stays in enqueued state. I've set the same network constraint as above and time of 15 minutes. But its a periodic request in my case. – Prasad Pawar Jan 29 '19 at 15:14

Why workers in work manager still in ENQUEUED state?

1 Answers1

Linked