I've got a Data Sync service that I'm moving to `WorkManager`, and it can potentially run for a long...

# android

[Adam Brown]

I've got a Data Sync service that I'm moving to WorkManager, and it can potentially run for a long time, so I launch it with setExpedited and setup the ForegroundInfo to display a progress notification and keep it foreground. But now it fails in Android 12+ because of the new restrictions. Is there now no way to launch a long running task like this from the background? i.e. schedule a job once a week to do a data sync and have it run foreground?

[Jakub Syty]

I'm also curious about that, because it does seem so...

[Jakub Syty]

I think the expedited work should be able to run from the background on android 12+, but i don't think there is a way to schedule a recurring long-running job

[Adam Brown]

ya, from what I'm reading that appears to be the case.

[Adam Brown]

I wonder if a background & non-expedited Worker could enqueue an expedited Worker :P

[Jakub Syty]

I doubt it, but it's worth a try 🙂

[Jakub Syty]

oh, no, i already tried that. You cannot schedule expedited job while in the background

[Adam Brown]

One (not great) option might be to post a notification from the background that tells the user some work needs to be done. When the user taps that notification, we launch the foreground Worker. As per the docs, if the foreground job is started from a user interaction on a Notification, it will be allowed