error: compiler message file broken: key=compiler.err.Processor
See original GitHub issueKotlin 2.61
A missing @Provides
annotation in Module on Dagger 2.17 results in error: compiler message file broken: key=compiler.err.Processor: org.jetbrains.kotlin.kapt3.base.ProcessorWrapper@550c0cf8 arguments={0}, {1}, {2}, {3}, {4}, {5}, {6}, {7}
A missing @Provides
annotation in Module on Dagger 2.15 results in a meaningful exception describing which dependency could not be provided
Issue Analytics
- State:
- Created 5 years ago
- Comments:19 (1 by maintainers)
Top Results From Across the Web
compiler message file broken: key=compiler.err.file : IDEA-2581
I get this error message sometimes when I compile. Relaunching makes it go away. compiler message file broken: key=compiler.err.file ...
Read more >java - Room - compiler message file broken - Stack Overflow
When I try to run application, I am getting following error: Compilation failed; see the compiler error output for details. It contains 1 ......
Read more >error: compiler message file broken: key=compiler.err.sun.io ...
... invoking javac an a fully compliant java source file, it comes from the encoding of the source not being the one used...
Read more >[JDK-8222754] Javac compiler message file broken
nformation:java: compiler message file broken: key=compiler.misc.msg.bug arguments=11.0.3, {1}, {2}, {3}, {4}, {5}, {6}, {7}
Read more >Bug ID: JDK-8194997 compiler message file broken
JDK-8194997 : compiler message file broken: key=compiler.misc.cant.resolve.args ... Priority: P3; Status: Resolved; Resolution: Duplicate; OS: generic; CPU: ...
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
I got the error because my base module had a dependency on
Room
but it was imported withimplementation
instead ofapi
So if you end up hitting this error, double check the libraries you’re trying to access and whether those are truly imported in the right modules or “re-exported” in submodules, depending on how you setup your gradle files.
What’s the status on this? I’ve been struggling for a long time getting an Instant App working and now most recently I got this error, and I’m writing it in Kotlin.