HiltWorkerFactory：在AppStartup配置WorkManagerInitializer

Question

HiltWorkerFactory：在AppStartup配置WorkManagerInitializer

androidkotlindependency-injectionandroid-workmanagerdagger-hilt

11

WorkManagerInitializer 需要配置 setWorkerFactory 来向 Worker 类注入依赖项。[文档][1] 解释了关于在 AppStartup 初始化 WorkManager，但没有提供有关如何配置 setWorkerFactory 的任何见解。如果有人能提出任何解决方案或解决方法，那将非常有帮助。问题是我无法将自己的依赖项注入到 workerClass 中。下面包含两个场景以解释此情况：

情景1：// 这个调用很好。

class AppWorker @WorkerInject constructor(
    @Assisted context: Context,
    @Assisted workerParams: WorkerParameters
) : Worker(context, workerParams) {
    companion object {
        val workType = "WorkType"

    }

    override fun doWork(): Result {
        return Result.success()
    }
}

失败场景＃2：

// Initializes WorkManager.
class WorkManagerInitializer : Initializer<WorkManager> {
    override fun create(context: Context): WorkManager { 
        // How to get workFactory required for configuration.
        var workerFactory: HiltWorkerFactory? = null
        val configuration = Configuration.Builder()
            .setWorkerFactory(workerFactory)
            .build()
        WorkManager.initialize(context, configuration)
        return WorkManager.getInstance(context)
    }

    override fun dependencies(): List<Class<out Initializer<*>>> {
        // No dependencies on other libraries.
        return emptyList()
    }
}



@HiltAndroidApp
class BaseApp: Application(),Configuration.Provider{
    @Inject lateinit var workerFactory: HiltWorkerFactory
    override fun getWorkManagerConfiguration() =
        Configuration.Builder()
            .setWorkerFactory(workerFactory)
            .build()
    init {
        Thread.setDefaultUncaughtExceptionHandler(ThreadExceptionalHandler())

    }
    override fun onCreate() {
        super.onCreate()
        if (BuildConfig.DEBUG) {
            Timber.plant(DebugTree())
        }
    }
}

清单文件.xml

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools"
    package="com.example.baseapp">

      <application
        android:name="com.example.baseapp.startup.BaseApp"
        android:allowBackup="true"
        android:icon="@mipmap/ic_launcher"
        android:label="@string/app_name"
        android:roundIcon="@mipmap/ic_launcher_round"
        android:supportsRtl="true"
        android:theme="@style/Theme.MyApp"
        >
        <activity android:name="com.example.baseapp.gui.activities.MainActivity"
            android:screenOrientation="portrait">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />

                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>

    <provider
            android:name="androidx.startup.InitializationProvider"
            android:authorities="${applicationId}.androidx-startup"
            android:exported="false"
            tools:node="merge">

            <meta-data                android:name="com.example.baseapp.startup.AppServicesInitializer"
                android:value="androidx.startup" />

        </provider>
        <provider
            android:name="androidx.work.impl.WorkManagerInitializer"
            android:authorities="${applicationId}.workmanager-init"
            tools:node="remove"/>

    </application>

</manifest>

// 应用程序编译和运行成功，但未能调用doWork()

  [1]: https://developer.android.com/topic/libraries/app-startup
The AppWorker class dowork() method is not getting called with WorkManagerInitializer defined at AppStartup. Here is the error in logcat:

2020-09-24 19:38:41.811 23803-23863/com.example.baseapp E/WM-WorkerFactory: Could not instantiate com.example.baselib.services.local.work_manager.worker.AppWorker
java.lang.NoSuchMethodException: com.example.baselib.services.local.work_manager.worker.AppWorker.<init> [class android.content.Context, class androidx.work.WorkerParameters]
    at java.lang.Class.getConstructor0(Class.java:2332)
    at java.lang.Class.getDeclaredConstructor(Class.java:2170)
    at androidx.work.WorkerFactory.createWorkerWithDefaultFallback(WorkerFactory.java:95)
    at androidx.work.impl.WorkerWrapper.runWorker(WorkerWrapper.java:242)
    at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:136)
    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:923)

- Chandra

4个回答

6

我们可以直接从Initializer中使用HiltWorkerFactory。以下是示例：

class CustomWorkManagerInitializer : Initializer<WorkManager> {

    override fun create(context: Context): WorkManager {
        val workerFactory = getWorkerFactory(appContext = context.applicationContext)
        val config = Configuration.Builder()
            .setWorkerFactory(workerFactory)
            .build()
        WorkManager.initialize(context, config)
        return WorkManager.getInstance(context)
    }

    override fun dependencies(): MutableList<Class<out Initializer<*>>> = mutableListOf()

    private fun getWorkerFactory(appContext: Context): HiltWorkerFactory {
        val workManagerEntryPoint = EntryPointAccessors.fromApplication(
            appContext,
            WorkManagerInitializerEntryPoint::class.java
        )
        return workManagerEntryPoint.hiltWorkerFactory()
    }

    @InstallIn(SingletonComponent::class)
    @EntryPoint
    interface WorkManagerInitializerEntryPoint {
        fun hiltWorkerFactory(): HiltWorkerFactory
    }
}

删除应用程序中的HiltWorkerFactory注入。

@HiltAndroidApp
class BaseApp : Application() {
    override fun onCreate() {
        super.onCreate()
        AppInitializer.getInstance(this).initializeComponent(CustomWorkManagerInitializer::class.java)
    }
}

同时禁用默认的WorkManager初始化器并在清单文件中添加我们自定义的。

<provider
        android:name="androidx.startup.InitializationProvider"
        android:authorities="${applicationId}.androidx-startup"
        android:exported="false"
        tools:node="merge">
        <!-- disable default -->
        <meta-data
            android:name="androidx.work.WorkManagerInitializer"
            android:value="@string/androidx_startup"
            tools:node="remove" />
        <!-- enable custom -->
        <meta-data
            android:name="com.acme.app.initializer.CustomWorkManagerInitializer"
            android:value="androidx.startup" />
</provider>

- vivanov

嗨，对我来说这个有效。谢谢!!! 我试图创建一个带有一些依赖项的新工作程序，但是Worker无法实例化。这挽救了我的一天！感谢@vivanov。 - danybarco

5

您可以使用以下方式简单地注入依赖项，通过使用@WorkerInject注释并摆脱您的工厂:

class ExampleWorker @WorkerInject constructor(
  @Assisted appContext: Context,
  @Assisted workerParams: WorkerParameters,
  dependency: YourClassDependency
) : Worker(appContext, workerParams) { ... }

然后，让您的 Application 类实现 Configuration.Provider 接口，注入一个 HiltWorkFactory 实例，并将其作为参数传递给 WorkManager 配置，如下所示：

@HiltAndroidApp
class ExampleApplication : Application(), Configuration.Provider {

  @Inject lateinit var workerFactory: HiltWorkerFactory

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

请注意，您还必须从AndroidManifest.xml中删除默认的初始化程序：

<application>
  <provider
      android:name="androidx.work.impl.WorkManagerInitializer"
      android:authorities="${applicationId}.workmanager-init"
      tools:node="remove" />
</application>

参考资料：Hilt 和 Jetpack 集成

- Nicola Gallazzi

我已经实现了您建议的将依赖项注入到WorkerClass的解决方案。但是，根据方案＃2中描述的方式，在WorkManagerInitializer中设置“HiltWorkerFactory”似乎是不可能的。 - Chandra

@Chandra，你能分享一下你的manifest.xml和应用程序类吗？ - Nicola Gallazzi

所有的 Hilt 依赖项，除了“Work Manager”之外，都在 AppStartup 中初始化。我已经注释掉了 WorkManagerInitializer 类的代码，以便在 Application 类中设置“HiltWorkerFactory”。 - Chandra

似乎你的应用程序仍在使用Scenario 2中描述的WorkManagerInitializer类。你能分享一个repo吗？ - Nicola Gallazzi

2

对于仍然遇到此问题的用户，如果要从AndroidManifest.xml中删除默认初始化程序，请更改以下内容：

<provider
    android:name="androidx.startup.InitializationProvider"
    android:authorities=\"${applicationId}.androidx-startup"
    android:exported="false"
    tools:node=\"merge">
    <!-- If you are using androidx.startup to initialize other components -->
    <meta-data
        android:name="androidx.work.impl.WorkManagerInitializer"
        android:value="androidx.startup"
        tools:node="remove" />
 </provider>

为了

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

区别在于 androidx.work.impl.WorkManagerInitializer 和 androidx.work.WorkManagerInitializer。

- Anthony Ngure

网页内容由stack overflow 提供, 点击上面的

可以查看英文原文，
原文链接

- Ace · Accepted Answer

对于使用 Hilt 和 androidx.work-* 版本 2.6.0-alpha01 或更高版本的用户:

根据发布说明，这个版本开始在内部使用新的 androidx.startup Jetpack 库。因此，从 AndroidManifest.xml 中删除 WorkManager 的默认初始化程序的方法有所变化。

如果您在应用程序中的其他位置使用了 androidx.startup，请使用以下内容替换旧更改:

<provider
    android:name="androidx.startup.InitializationProvider"
    android:authorities="${applicationId}.androidx-startup"
    android:exported="false"
    tools:node="merge">
    <!-- If you are using androidx.startup to initialize other components -->
    <meta-data
        android:name="androidx.work.impl.WorkManagerInitializer"
        android:value="androidx.startup"
        tools:node="remove" />
 </provider>

否则，你可以通过替换旧变更来完全禁用 androidx.startup ：

<!-- If you want to disable androidx.startup completely. -->
<provider
    android:name="androidx.startup.InitializationProvider"
    android:authorities="${applicationId}.androidx-startup"
    tools:node="remove">
</provider>

这样，你的HiltWorker将再次使用你子类化的应用程序中的工厂。不幸的是，你会失去延迟启动的（明显）好处。