Hilt: Compiler processor doesn't recognize options dagger.fastInit, dagger.hilt.android.internal.disableAndroidSuperclassValidation
See original GitHub issueHello.
I am developing multi-module Android project with Hilt version 2.28.3-alpha
. I have included dagger compiler to every module which requests or provides. After compilation in Android studio 4.0.1
I see warnings
in every module:
warning: The following options were not recognized
by any processor: '[dagger.fastInit, dagger.hilt.android.internal.disableAndroidSuperclassValidation, kapt.kotlin.generated]'
Though these are warnings
I was taught to pay attention to them as well, since they might indicate a potential problem with logic or performance, or anything else.
Applications seems to compile and run successfully, but are these warnings important? May be I am missing some Dagger Hilt
setting?
Thank you.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:17
- Comments:10 (1 by maintainers)
Top Results From Across the Web
The following options were not recognized by any processor ...
That happens when you compile a multi module project and some module has kapt but no entry point. The issue is described here...
Read more >The following options were not recognized by any processor...
warning: The following options were not recognized by any processor: '[dagger.fastInit, dagger.hilt.android.internal.disableAndroidSuperclassValidation ...
Read more >Gradle Build Setup - Dagger
The Hilt Gradle plugin offers an option for performing Hilt's classpath aggregation in a dedicated Gradle task. This allows the Hilt annotation processors...
Read more >Fix Hilt Android Gradle plugin is applied but no ... - YouTube
Sometimes, when importing an Hilt Android project, you get this error: ... plugin is applied but no com.google. dagger : hilt - android...
Read more >Dependency injection with Hilt | Android Developers
Hilt is built on top of the popular DI library Dagger to benefit from the ... lifecycle callback an Android class gets injected...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Could it be that a module that reports this doesn’t use some of the Hilt features? Maybe the module that reports this doesn’t use any
@AndroidEntryPoint
? Just guessing, I haven’t checked that assumption at all.I had same problem. added: id ‘com.google.dagger.hilt.android’ to build gradle and it works