WorkManager Worker class not running after App kills

Question

I am extending the Worker class and in its doWork() method I'm uploading files to the cloud. The app uploads files when it is in foreground, but If I kill the app the doWork process stops. After opening the app again, it starts to run and completes the task. This means it was not running in the background. I want to run a worker thread even if app is not in the foreground. Should I add something into the manifest file or any flag to the Activity. Any help will be appreciated.

The dowork() method can be called from the uploadworker instance.

OneTimeWorkRequest uploadworker = new OneTimeWorkRequest.Builder(VideoUploadWorker.class)
    .build();
WorkManager.getInstance().enqueue(uploadworker);

This code is working perfectly when app is in foreground. I tested in many devices but I got same results.

I use it with a foreground service, themes like the only way to make it run in background. But even this way without acquiring wakelock, it will suffer from doze mode — Vladyslav Matviienko, May 28 '19 at 11:18
@Quicklearner I tested in Samsung,Pixel and infocus & api level 23,26,27 — Narender Reddy, May 28 '19 at 11:24
@VladyslavMatviienko can u please elaborate how to combine Worker class and foreground service. — Narender Reddy, May 28 '19 at 11:28
you don't need to combine them in fact. You need to run the foreground service to prevent your app from being killed. — Vladyslav Matviienko, May 28 '19 at 11:29
@VladyslavMatviienko thanks for your suggestion.I will try this — Narender Reddy, May 28 '19 at 11:31
I write Service with retruning Sticky intent and startcommand method i start the worker class.in workerclass dowork method i am uploading file.But when i close the app file not uploading — Narender Reddy, May 28 '19 at 13:01
that is not enough to start foreground service. You need not just a service, but a foreground service — Vladyslav Matviienko, May 28 '19 at 14:17
public class VideoUploadService extends Service { Override public int onStartCommand(Intent intent, int flags, int startId) { OneTimeWorkRequest uploadworker = new OneTimeWorkRequest.Builder(VideoUploadWorker.class) .build(); WorkManager.getInstance().enqueue(uploadworker); Log.i("Service","StartCommand"); return START_STICKY; } @Override public IBinder onBind(Intent intent) { return null; } } — Narender Reddy, May 29 '19 at 07:04
If you are already using a foreground service, why use WorkManager for one time, why not just do it with the service itself? It might help if you can include the code for your foreground service. — fsljfke, Sep 04 '20 at 15:18

WorkManager Worker class not running after App kills

0 Answers0