在 ContentProvider 中获取 WorkManager 实例
Get WorkManager instance in a ContentProvider
我想在内容提供商中安排任务:
class LogProvider : ContentProvider() {
override fun onCreate(): Boolean {
Log.i("Lagg", "Initializing LogCollection")
return try {
context?.let { LogCollectionInitializer().initializeCollector(it) }
true
} catch (e: Exception) {
false
}
}
// ...
}
初始化程序安排工作的位置:
WorkManager.getInstance()
.enqueueUniquePeriodicWork(
CleanLogDatabaseTask.DB_CLEANER_TASK_NAME,
ExistingPeriodicWorkPolicy.KEEP,
PeriodicWorkRequestBuilder<CleanLogDatabaseTask>(DB_CLEANING_INTERVAL, TimeUnit.MILLISECONDS)
.setBackoffCriteria(BackoffPolicy.LINEAR, PeriodicWorkRequest.MIN_BACKOFF_MILLIS, TimeUnit.MILLISECONDS)
.build()
)
问题是我得到这个错误:
java.lang.IllegalStateException: WorkManager is not initialized properly. The most likely cause is that you disabled WorkManagerInitializer in your manifest but forgot to call WorkManager#initialize in your Application#onCreate or a ContentProvider.
- 不,我没有禁用 WorkManager init。到底是什么导致了这个问题?
当我从内容提供商访问 workManager 时,我应该采取不同的行动吗?
众所周知,WorkManager 有自己的内容提供程序。因此,如果您覆盖它并将其优先级设置得更高,它将在其他提供程序之前被初始化。所以在这里:
android:name="androidx.work.impl.WorkManagerInitializer"
android:authorities="${applicationId}.workmanager-init"
android:initOrder="11"
android:enabled="true"
android:exported="false" /> ```
我想在内容提供商中安排任务:
class LogProvider : ContentProvider() {
override fun onCreate(): Boolean {
Log.i("Lagg", "Initializing LogCollection")
return try {
context?.let { LogCollectionInitializer().initializeCollector(it) }
true
} catch (e: Exception) {
false
}
}
// ...
}
初始化程序安排工作的位置:
WorkManager.getInstance()
.enqueueUniquePeriodicWork(
CleanLogDatabaseTask.DB_CLEANER_TASK_NAME,
ExistingPeriodicWorkPolicy.KEEP,
PeriodicWorkRequestBuilder<CleanLogDatabaseTask>(DB_CLEANING_INTERVAL, TimeUnit.MILLISECONDS)
.setBackoffCriteria(BackoffPolicy.LINEAR, PeriodicWorkRequest.MIN_BACKOFF_MILLIS, TimeUnit.MILLISECONDS)
.build()
)
问题是我得到这个错误:
java.lang.IllegalStateException: WorkManager is not initialized properly. The most likely cause is that you disabled WorkManagerInitializer in your manifest but forgot to call WorkManager#initialize in your Application#onCreate or a ContentProvider.
- 不,我没有禁用 WorkManager init。到底是什么导致了这个问题?
当我从内容提供商访问 workManager 时,我应该采取不同的行动吗?
众所周知,WorkManager 有自己的内容提供程序。因此,如果您覆盖它并将其优先级设置得更高,它将在其他提供程序之前被初始化。所以在这里:
android:name="androidx.work.impl.WorkManagerInitializer"
android:authorities="${applicationId}.workmanager-init"
android:initOrder="11"
android:enabled="true"
android:exported="false" /> ```