Android Periodic WorkManager周期性执行失效问题求助

我尝试用Dagger Hilt依赖注入运行PeriodicWork，但任务无法周期性执行。检查代码后发现，最多只能看到一次任务执行成功的日志，尽管预期是每秒收到一次执行消息。

MainActivity代码 #

@AndroidEntryPoint
class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        setContent {
            RunARepeatableWorkUsingWorkManagerTheme {

            val lifecycleOwner = LocalLifecycleOwner.current

            LaunchedEffect(key1 = Unit ){

                val workRequest = PeriodicWorkRequestBuilder<CustomWorker>(
                    repeatInterval = 1,
                    repeatIntervalTimeUnit = TimeUnit.SECONDS,)
                    .setBackoffCriteria(
                        backoffPolicy = BackoffPolicy.LINEAR,
                        duration = Duration.ofSeconds(5))
                    .build()

                    val workManager = WorkManager.getInstance(applicationContext)
                    workManager.enqueueUniquePeriodicWork("myWork", ExistingPeriodicWorkPolicy.KEEP, workRequest)

                     workManager.getWorkInfosForUniqueWorkLiveData("myWork")
                    .observe(lifecycleOwner){ it ->
                        it.forEach {workInfo ->
                        Log.d("MyWorker: MainActivity", "${workInfo.state}")
                    }
                }
            }
            }
        }
    }
}   

CustomWorker代码 #

@HiltWorker
class CustomWorker @AssistedInject constructor(
    @Assisted context: Context,
    @Assisted workerParameters: WorkerParameters
) : CoroutineWorker(context, workerParameters){
        override suspend fun doWork(): Result {
            try {
                println("MyWorker : The result or the worker is Success")
                return Result.success()
            } catch (e: Exception) {
                Log.e("MyWorker: CustomWorker", "Worker failed: ${e.message}", e)
                return Result.failure()
            }
        }
}

AppInstance代码 #

@HiltAndroidApp
class AppInstance : Application(), Configuration.Provider{
    @Inject lateinit var workerFactory: HiltWorkerFactory

    override fun getWorkManagerConfiguration() =
        Configuration.Builder()
            .setWorkerFactory(workerFactory)
            .build()

}

清单文件配置 #

<provider
    android:name="androidx.startup.InitializationProvider"
    android:authorities="${applicationId}.androidx-startup"
    android:exported="false"
    tools:node="merge"
    >
    <meta-data
        android:name="androidx.work.impl.WorkManagerInitializer"
        android:value="androidx.startup"
        tools:node="remove" />
</provider>

Logcat输出 #

2023-09-24 18:16:46.712  4819-4819  MyWorker: MainActivity  com...epeatableworkusingworkmanager  D  ENQUEUED
2023-09-24 18:17:47.375  4819-4854  System.out              com...epeatableworkusingworkmanager  I  MyWorker : The result or the worker is Success
2023-09-24 18:17:47.429  4819-4819  MyWorker: MainActivity  com...epeatableworkusingworkmanager  D  RUNNING
2023-09-24 18:17:47.437  4819-4819  MyWorker: MainActivity  com...epeatableworkusingworkmanager  D  ENQUEUED

核心原因 #

• WorkManager的周期任务最小间隔限制：Android系统对PeriodicWorkRequest有强制的最小周期限制——Android 7.1（API 25）及以上版本为15分钟，即使你设置了1秒的间隔，系统也会自动忽略这个值，改用允许的最小周期。这是系统为平衡功能和设备资源消耗做出的限制。
• 日志显示的误导：日志最后显示任务回到ENQUEUED状态，说明任务已经被重新排队，但受限于最小周期，不会立即执行，所以你看不到每秒的执行日志。

解决办法 #

1. 测试阶段用OneTimeWorkRequest模拟短间隔执行 #

如果只是为了验证任务的重复执行逻辑，可以放弃PeriodicWorkRequest，改用OneTimeWorkRequest，在任务执行完成后手动调度下一次任务：

@HiltWorker
class CustomWorker @AssistedInject constructor(
    @Assisted context: Context,
    @Assisted workerParameters: WorkerParameters,
    private val workManager: WorkManager // 通过Hilt注入WorkManager
) : CoroutineWorker(context, workerParameters){
        override suspend fun doWork(): Result {
            try {
                Log.d("MyWorker: CustomWorker", "The result or the worker is Success")
                // 调度下一次任务，实现短间隔重复
                val nextWork = OneTimeWorkRequestBuilder<CustomWorker>().build()
                workManager.enqueue(nextWork)
                return Result.success()
            } catch (e: Exception) {
                Log.e("MyWorker: CustomWorker", "Worker failed: ${e.message}", e)
                return Result.failure()
            }
        }
}

同时在MainActivity里只需要启动一次任务：

val workRequest = OneTimeWorkRequestBuilder<CustomWorker>().build()
workManager.enqueueUniqueWork("myWork", ExistingWorkPolicy.KEEP, workRequest)

2. 正式环境遵守系统周期限制 #

如果是正式业务需求，需要接受15分钟的最小周期，或者根据业务场景调整间隔到符合系统要求的值（比如设置为15分钟及以上）。

3. 日志优化 #

将doWork里的println替换为Log.d，这样日志会和MainActivity的日志统一，更容易追踪任务执行状态：

Log.d("MyWorker: CustomWorker", "The result or the worker is Success")

额外说明 #

• 你的Hilt配置（AppInstance和清单文件）是正确的，任务能执行一次就证明依赖注入没有问题。
• LaunchedEffect(key1 = Unit)的使用是合理的，它会在Activity创建时执行一次，且因为用了ExistingPeriodicWorkPolicy.KEEP，即使Activity重建也不会重复创建任务。

内容的提问来源于stack exchange，提问作者Евгений s