我想将WorkManager与Dagger 2一起使用,以将依赖项注入工作程序中。我按照this article进行了设置。设置的一部分是按需初始化。为此,我在清单文件中添加了以下几行:
<provider
android:name="androidx.work.impl.WorkManagerInitializer"
android:authorities="${applicationId}.workmanager-init"
android:exported="false"
tools:node="remove" />
并使我的应用程序类实现Configuration.Provider
接口,如下所示:
@NonNull
@Override
public Configuration getWorkManagerConfiguration() {
return new Configuration.Builder().setMinimumLoggingLevel(Log.DEBUG).setWorkerFactory(delegatingWorkerFactory).build();
}
匕首设置按预期工作。
但是,我遇到以下问题:在Application#onCreate
中,我加入了唯一的定期任务,并且在首次安装应用程序时,此操作始终失败,并出现以下错误:
java.lang.IllegalStateException: The file system on the device is in a bad state. WorkManager cannot access the app's internal data store.
at androidx.work.impl.utils.ForceStopRunnable.run(ForceStopRunnable.java:115)
at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:211)
at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:195)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:503)
at android.database.sqlite.SQLiteConnectionPool.tryAcquireNonPrimaryConnectionLocked(SQLiteConnectionPool.java:987)
at android.database.sqlite.SQLiteConnectionPool.waitForConnection(SQLiteConnectionPool.java:693)
at android.database.sqlite.SQLiteConnectionPool.acquireConnection(SQLiteConnectionPool.java:378)
at android.database.sqlite.SQLiteSession.acquireConnection(SQLiteSession.java:894)
at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:586)
at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:58)
at android.database.sqlite.SQLiteQuery.<init>(SQLiteQuery.java:37)
at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:46)
at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1408)
at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1383)
at androidx.sqlite.db.framework.FrameworkSQLiteDatabase.query(FrameworkSQLiteDatabase.java:161)
at androidx.room.RoomDatabase.query(RoomDatabase.java:328)
at androidx.room.util.DBUtil.query(DBUtil.java:83)
at androidx.work.impl.model.PreferenceDao_Impl.getLongValue(PreferenceDao_Impl.java:70)
at androidx.work.impl.utils.PreferenceUtils.getNeedsReschedule(PreferenceUtils.java:96)
at androidx.work.impl.utils.ForceStopRunnable.shouldRescheduleWorkers(ForceStopRunnable.java:187)
at androidx.work.impl.utils.ForceStopRunnable.run(ForceStopRunnable.java:88)
at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
如果我将使工作排队的代码从Application#onCreate
移到应用程序生命周期的后期(例如某些活动),那么它不会失败。
我没有发现Application#onCreate
对工作入队的任何限制,因此我希望它一定可以工作。
我正在使用WorkManager 2.3.4和Room 2.2.5。我也尝试将Room降级为2.2.2,并将WorkManager降级为几个较旧的稳定版本,但这没有帮助。在具有不同Android版本的不同设备和仿真器上都可以重现该问题。
我该如何解决此问题并继续在Application#onCreate
中加入工作?
编辑 这是我对工作的征服方式:
workManagerProvider.get().enqueueUniquePeriodicWork(
"Unique name",
ExistingPeriodicWorkPolicy.REPLACE,
request
)
其中workManagerProvider
是Provider<WorkManager>
。由于循环依赖,我无法直接访问工作管理器,因此我只能从dagger获取提供程序,然后才能使用它。与主题无关。
答案 0 :(得分:0)
问题出在第一次启动时,另一段代码擦除了应用程序的内部数据。它确实与WorkManager
创建数据库的过程并行进行,但是在某些情况下,导致某些工作管理器访问了已删除的数据库文件。