Is it true that starting from Hilt version 2.45, the compiler cannot pass the arguments parameter of the project kapt?

[xuexixuexijpg]

The following picture is my builde gradle parameters:

Output parameter diagram when executing kaptDebugKotlin task:

Output parameter diagram when executing hiltJavaCompileDebug task:

From the hiltJavaCompileDebug task, some project parameters are missing, which leads to errors in the judgment of project parameters obtained by Processors of other frameworks.

The following is one way to write the example. The temporary solution is to change other people's processing to prohibit throwing errors. I don't know why Hilt does not pass the project's arguments parameter.

[danysantiago]

This is indeed a bug where Hilt's final JavaCompileTask includes annotation processors configured by the users in KAPT / KSP but does not also copy processor arguments.

You should be able to workaround this by finding the task and applying the options:

// in a build.gradle.kts
tasks.withType<JavaCompile>().configureEach {
    if (name.startsWith("hiltJavaCompile")) {
        options.compilerArgs.add("-AModuleName=app")
    }
}