Android Oreo service restriction affect intentservices from job schedulers?

Question

With the new background service restrictions introduced in Oreo, I'm having a hard time finding a place to clarify whether IntentServices can still be launched from a JobScheduler while the app is backgrounded.

I have a very important feature based around geofencing that needs to run an intentService after a fence is broken. I spent a long time setting it up to queue up jobs when fences are broken and the app is in DOZE for Nougat. When the job is finally run by the OS when the window of network connection is reopened, I spin off each job one after the other in an intentService. Can I no longer do this now that I'm technically starting a service while the app is not in the foreground or is this still permitted since I'm using the JobScheduler?

Answer 1

You should not assume that your app is able to start services from a job. In particular, apps are frequently still in a background state when their jobs execute, and calling startService() while in a background state will throw an exception. Of course, it is always legal to call startForegroundService(); though obviously this has UI implications as well.

JobIntentService is explicitly intended to replace IntentService in a way that is compatible with Android O+ background restrictions. You should look into switching to that instead of using the legacy IntentService support class.

Answer 2

read this article [Exploring Background Execution Limits on Android Oreo]

https://medium.com/exploring-android/exploring-background-execution-limits-on-android-oreo-ab384762a66c hope it will answer your question

Answer 3

For API 25 and below use background Service or IntentService with a regular startService() call.

For API 26 and above use startForegroundService().

You can also choose to use androidx.core.app.JobIntentService which is using JobScheduler for API 26+, and background service for API 25 and below.