Android Workmanager run job in a fixed process

Question

I have a background task that has to run in a fixed process. I'm currently using a JobIntentService for this. However, I'd like to migrate to WorkManager to make use of network based task delays.

Is there any solution to this either using WorkManager or in any other API 14-28 compatible way?

Anyone help with question, is it possible to run work manger in separate process? — Mahesh, Sep 14 '18 at 11:48

score 1 · Answer 1 · answered Dec 25 '20 at 09:12

New in WorkManager 2.5.0, there is a workmanager-multiprocess module to solve this problem. You can implement this with implementation "androidx.work:work-multiprocess:$work_version"

To use this, you can register a new WorkManager.Initializer as detailed in this page: https://developer.android.com/topic/libraries/architecture/workmanager/advanced/custom-configuration

When you register this initializer, your configurations need to include a call to .setDefaultProcessName("com.example.app:processName"). This will make the calls occur in the correct process. I am testing this out right now, and it seems to be working, but I'll update this post if there are any issues.

score 0 · Answer 2 · answered Apr 25 '19 at 18:17

What about this approach:


        <service
                android:name="androidx.work.impl.background.systemjob.SystemJobService"
                android:process=":worker"/>

Just put the declaration into your Manifest and ManifestMerger creates a final merged Manifest with android:process=":worker" (worker is a name of non-main process, can be another one)

score -1 · Answer 3 · answered Aug 14 '18 at 19:52

-1

have a look at this work manager for network calls sample

answered Aug 14 '18 at 19:52

stevandoh

47
1
1

This doesn't seem to control which process it is run in. – F43nd1r Aug 14 '18 at 23:46

Android Workmanager run job in a fixed process

3 Answers3

Linked