blocks|key|881590|text|似乎，有一个缺陷与kapt，项目清理应该有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|881591|./gradlew+clean|code-block|syntax|javascript|881592|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

It seems, there is a bug with kapt, project cleaning should help.

<pre><code>./gradlew clean
</code></pre>

blocks|key|2215710|text|根本原因|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2215711|基本上，在使用kapt.时修复这个没有什么可做的引用在使用预处理器(+此链接+)的另一个库中解决相同问题的此链接：|offset|length|style|BOLD|CODE|2215712|因为Kotlin在运行Java之前就做了存根，所以Kotlin对OrmaDatabase一无所知，存根中的声明名将是error.NonExistentClass。这会破坏注释处理工具。这是一种kapt限制|blockquote|2215713|如何修复它(解决方法)|2215714|只需使用普通的apt或annotationProcessor来运行Dagger编译器。一旦我改变了：|2215715|kapt+libs.daggerCompiler|code-block|syntax|javascript|2215716|至|2215717|annotationProcessor+libs.daggerCompiler|2215718|在我的模块级build.gradle文件中，我能够获得这些错误。修复错误后，必须将该行恢复为kapt，否则将不会生成匕首类，因为它们是在Kotlin中定义的。|2215719|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/gen0083/KotlinDaggerDataBinding/blob/master/README.md|1^0|0|7|4|H|14|7|4|Z|3|0|1H|3|1|0|0|2U|0|0|B|0|0|1E|7|3|B|J|0|0|0|1|0|0|0|27|6|C|1A|4|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@$D|1B|E|1C|F|G]|$D|1D|E|1E|F|G]|$D|1F|E|1G|F|H]]|9|@$D|1H|E|1I|1|1J]|$D|1K|E|1L|1|1M]]|A|$]]|$1|I|3|J|5|K|7|1N|8|@$D|1O|E|1P|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1Q|8|@$D|1R|E|1S|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1T|8|@$D|1U|E|1V|F|G]|$D|1W|E|1X|F|H]|$D|1Y|E|1Z|F|H]]|9|@]|A|$]]|$1|P|3|Q|5|R|7|20|8|@]|9|@]|A|$S|T]]|$1|U|3|V|5|6|7|21|8|@$D|22|E|23|F|G]]|9|@]|A|$]]|$1|W|3|X|5|R|7|24|8|@]|9|@]|A|$S|T]]|$1|Y|3|Z|5|6|7|25|8|@$D|26|E|27|F|G]|$D|28|E|29|F|H]|$D|2A|E|2B|F|H]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]|18|$5|13|14|15|A|$16|17]]]]

<h2>The Root Cause</h2>

Basically, there's not much that can be done to fix this when using <code>kapt</code>. To quote <a href="https://github.com/gen0083/KotlinDaggerDataBinding/blob/master/README.md" rel="noreferrer">this link</a> that tackles the same problem in another library that uses pre-processors (OrmaDatabase):

<blockquote>
 Because Kotlin makes its stubs before Java Annotation Processing runs,
 Kotlin knows just nothing about OrmaDatabase, and the name of the
 declaration in stubs will be error.NonExistentClass. This breaks the
 Annotation Processing tool. It's a kind of kapt limitation
</blockquote>

<h2>How to fix it (the workaround)</h2>

Just use plain <code>apt</code> or <code>annotationProcessor</code> for running Dagger compiler. As soon as I changed:

<pre><code>kapt libs.daggerCompiler
</code></pre>

to 

<pre><code>annotationProcessor libs.daggerCompiler
</code></pre>

in my module level <code>build.gradle</code> file, I was able to get the errors. After you've fixed the errors, you gotta revert the line back to <code>kapt</code> because otherwise dagger classes wouldn't be generated since they're defined in Kotlin.

blocks|key|2215774|text|我发现如果你用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2215775|kapt+{
++++generateStubs+=+true
}|code-block|syntax|javascript|2215776|更改为false将显示实际错误，一旦Dagger图的编译问题得到纠正，您可能会遇到问题，但只需将其更改为true，您就应该很好了|2215777|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I've found if you're using
<pre><code>kapt {
 generateStubs = true
}
</code></pre>
changing to false will then present the actual error, you will probably have issues building the Dagger Graph once it's compilation issues have been corrected, but simply change back to true, and you should be good

blocks|key|2215856|text|tldr:在annotationProcessor中将kapt更改为build.gradle，您将看到真正的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2215857|我得到了同样的错误，结果我只是注释掉了我在我的AppComponent中使用的一个类。不幸的是，kapt工具没有给我正确的错误信息。如果您在库的编译器中将kapt更改为annotationProcessor，并尝试构建，它也不会成功，但您将得到更详细的错误消息。|2215858|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

tldr: Change kapt to annotationProcessor in build.gradle and you will see the real problem.

I got the same error, and it turned out that I just commented out a class that I was using in my AppComponent. Unfortunately the kapt tool didn't give me the proper error message. If you change the kapt to annotationProcessor at your library's compiler, and try to build, it won't succeed neither, but you will get a more detailed error message.

blocks|key|881735|text|我在一个使用Dagger的多模块项目中遇到了一个非常类似的NonExistentClass错误，结果我忘记添加kotlin库依赖项。因此，在子模块中添加它就解决了我的问题：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|881736|implementation+"org.jetbrains.kotlin:kotlin-stdlib-jdk7:$rootProject.kotlinVersion"|code-block|syntax|javascript|881737|entityMap^0|T|G|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

I had a very similar situation with a <code>NonExistentClass</code> error in a multi-module project using Dagger and turns out I forgot to add the kotlin library dependency. So, just adding it in the sub-module solved my problem:

<pre><code>implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$rootProject.kotlinVersion"
</code></pre>

blocks|key|2177585|text|我最近也有同样的问题。当我有时通过Android+(3.4.c6)提交时，我使用“优化导入”选项来删除未使用的导入。出于某种原因，它删除了Parcelize注释的导入。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2177586|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue recently. As I sometimes commit through the Android Studio (3.4.c6) I use the "Optimize imports" option to remove unused imports. For some reason, it removed the import for the Parcelize annotation.

blocks|key|2215938|text|只需将其添加到构建gradle文件，以避免与NonExistentClass相关的问题|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2215939|kapt+{
++++correctErrorTypes+true+
}+|code-block|syntax|javascript|2215940|https://kotlinlang.org/docs/reference/kapt.html#non-existent-type-correction|2215941|entityMap|0|LINK|mutability|MUTABLE|url^0|M|G|0|0|0|24|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|W|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|M|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|L]]]]

Just add this to build gradle file to avoid the issues related <code>NonExistentClass</code>
<pre><code>kapt {
 correctErrorTypes true 
} 
</code></pre>
<a href="https://kotlinlang.org/docs/reference/kapt.html#non-existent-type-correction" rel="noreferrer">https://kotlinlang.org/docs/reference/kapt.html#non-existent-type-correction</a>

blocks|key|2177631|text|我升级了.gradle版本后，出现了错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2177632|将mockito的版本从2.7.21升级到2.%2B，为我解决了这个问题。|2177633|-++++androidTestCompile+"org.mockito:mockito-android:2.7.21"+//+remove+this
%2B++++androidTestCompile+"org.mockito:mockito-android:2.%2B"++++//+add+this|code-block|syntax|javascript|2177634|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

It appeared the errors after I upgraded the .gradle version.

Upgraded the version for mockito from 2.7.21 to 2.+ fixed the issue for me.

<pre><code>- androidTestCompile "org.mockito:mockito-android:2.7.21" // remove this
+ androidTestCompile "org.mockito:mockito-android:2.+" // add this
</code></pre>

blocks|key|881906|text|如果您在Android迁移之后遇到了这个问题，并开始在这里失去意识，那么您可以尝试一件事。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|881907|我的案子：|881908|我们的项目中只有几个模块，让我们称之为myModuleProject之一。迁移到Android之后，如果我从android运行它，编译和运行都很好，但是当代码转移到云和CI开始构建时，它在':myModuleProject:kaptDebugKotlin'中失败了，并且出现了很多错误，例如|offset|length|style|CODE|881909|e:+/home/circleci/code/myModuleProject/build/tmp/kapt3/stubs/debug/package_name_here/reporter/bindingadapter/SomeBindingAdapterKt.java:14:+error:+incompatible+types:+NonExistentClass+cannot+be+converted+to+Annotation
@error.NonExistentClass()|code-block|syntax|javascript|881910|经过两天的噩梦，我发现不仅根项目gradle.properties，而且模块项目应该包括以下！|881911|android.databinding.enableV2=true
android.useAndroidX=true
android.enableJetifier=true|881912|entityMap^0|0|0|J|F|2M|Y|0|0|G|H|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@$F|X|G|Y|H|I]|$F|Z|G|10|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|11|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|12|8|@$F|13|G|14|H|I]]|9|@]|A|$]]|$1|Q|3|R|5|L|7|15|8|@]|9|@]|A|$M|N]]|$1|S|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|T|$]]

If you come across this problem after Android X migration and start loosing your mind here is one thing you can try. 

<h2>My Case:</h2>

Our project had few modules in it, lets call one of them <code>myModuleProject</code>.
After migration to Android X it was compiling and running fine if I run it from android studio, but when code moved to cloud and CI starts build, it was failing with <code>':myModuleProject:kaptDebugKotlin'</code> and with long list of errors such as 

<pre><code>e: /home/circleci/code/myModuleProject/build/tmp/kapt3/stubs/debug/package_name_here/reporter/bindingadapter/SomeBindingAdapterKt.java:14: error: incompatible types: NonExistentClass cannot be converted to Annotation
@error.NonExistentClass()
</code></pre>

After two days of nightmare I found that not only root project <code>gradle.properties</code> but also module projects should include following!

<pre><code>android.databinding.enableV2=true
android.useAndroidX=true
android.enableJetifier=true
</code></pre>

blocks|key|2216018|text|在我的例子中，我有来自support-annotations的@Nullable注释，而我已经删除了它，以便迁移到AndroidX。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2216019|生成时，由于注释未正确导入，因此被检测为无效。|2216020|我所做的就是检查代码并修复所有导入。|2216021|entityMap^0|B|J|V|9|1L|8|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|D]|$9|R|A|S|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|T|8|@]|E|@]|F|$]]|$1|I|3|J|5|6|7|U|8|@]|E|@]|F|$]]|$1|K|3|-4|5|6|7|V|8|@]|E|@]|F|$]]]|L|$]]

In my case, I had <code>@Nullable</code> annotation from support-annotations while I had removed it in order to migrate to <code>AndroidX</code>. 
When building, because the annotation was not imported correctly, it was detected as invalid.

What I did was to check the code and fix all imports.

blocks|key|2177711|text|似乎kapt无法找到该类，也无法确定要使用哪个类。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2177712|import+foo.*++//+class+foo.Abc
import+bar.*++//+annotation+bar.Abc

@Abc
class+Xyz+{+...+}|code-block|syntax|javascript|2177713|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

It seems kapt cannot find the class, or cannot determine which class to use. e.g.

<pre><code>import foo.* // class foo.Abc
import bar.* // annotation bar.Abc

@Abc
class Xyz { ... }
</code></pre>

blocks|key|2177734|text|当我错误地将一个测试类移到我的主源集中时，我得到了这个错误。将其移回测试源集，消除了错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2177735|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I got this error when I had moved by mistake a test class into my main sourceset. Moving it back to the test sourceset got rid of the error.

blocks|key|2216105|text|当我的注入类中有编译错误时，我收到了这个错误。请确保没有任何编译错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2216106|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I received this error, when there was a compilation error in my Injected class. Please ensure that there aren't any compilation errors.

blocks|key|882053|text|我有一个项目，在Dagger向演讲者中注入一些东西的时候，我得到了一个持久的"NonExistentClass.java:3:+error:+error.NonExistentClass+must+be+INTERFACE"错误|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|882054|根本原因是微不足道的:一个带有不满意依赖项的有效@Inject注解文件的流氓副本不知怎么溜进了项目中。我们怎么能找到它？Android中的项目看起来不错。|882055|查看错误消息，它看起来如下：
/home/alex/AndroidProvects/TopProject/app/build/tmp/kapt3/stubs/onlineDebug/error/NonExistentClass.java:3:错误:+error.NonExistentClass必须是接口公共最终类NonExistentClass+{|ordered-list-item|882056|在/home/alex/AndroidProvects/TopProject/app/build/tmp/kapt3/stubs/onlineDebug/app编译的kapt文件中搜索"NonExistentClass“字符串|882057|您会发现确切的文件与不满意的Dagger依赖(在我的例子中，它是一个流氓孤儿文件在不应该存在的地方)|882058|entityMap^0|12|22|0|0|0|1|23|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$]]|$1|K|3|L|5|J|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|M|3|N|5|J|7|Y|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|P|$]]

I had a project with Dagger injecting something into Presenters
At one moment I got a persistent
<code>&quot;NonExistentClass.java:3: error: error.NonExistentClass must be INTERFACE&quot;</code> error
The root cause was trivial: a rogue copy of the valid @Inject annotated file with unsatisfied dependencies somehow slipped into the project. How can we find it? The project in Android Studio looks OK.
<ol>
<li>Look at the error message, it looks like:
/home/alex/AndroidProvects/TopProject/app/build/tmp/kapt3/stubs/onlineDebug/error/NonExistentClass.java:3: error: error.NonExistentClass must be INTERFACE
public final class NonExistentClass {
</li>
<li>Search at the compiled by kapt build files in
<code>/home/alex/AndroidProvects/TopProject/app/build/tmp/kapt3/stubs/onlineDebug</code>/app for &quot;NonExistentClass&quot; string
</li>
<li>You will find the exact file with the exact unsatisfied Dagger dependency (in my case it was a rogue orphan file in the place where it shouldn't exist)
</li>
</ol>

blocks|key|2216120|text|我和匕首也有类似的问题。添加以下内容有助于解决这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2216121|//+dagger
implementation+dep('com.google.dagger:dagger')
implementation+dep('com.google.dagger:dagger-android-support')
implementation+dep('com.spotify.dagger.android:dagger')
kapt+dep('com.google.dagger:dagger-android-processor')
kapt+dep('com.google.dagger:dagger-compiler')|code-block|syntax|javascript|2216122|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I had similar issues with dagger. Adding the following helped solve it :
<pre><code>// dagger
implementation dep('com.google.dagger:dagger')
implementation dep('com.google.dagger:dagger-android-support')
implementation dep('com.spotify.dagger.android:dagger')
kapt dep('com.google.dagger:dagger-android-processor')
kapt dep('com.google.dagger:dagger-compiler')
</code></pre>

blocks|key|2177851|text|在删除之后，过时的图书馆|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2177852|implementation+'androidx.hilt:hilt-lifecycle-viewmodel:1.0.0-alpha03'
kapt+'androidx.hilt:hilt-compiler:1.0.0-alpha03'|code-block|syntax|javascript|2177853|我发现了一个错误：|2177854|incompatible+types:+NonExistentClass+cannot+be+converted+to+Annotation+|2177855|看着https://dagger.dev/hilt/view-model.html，我换了一个ViewModel|style|CODE|2177856|class+MainViewModel+@ViewModelInject+constructor(
++++...
)+:+ViewModel()+{|2177857|至|2177858|@HiltViewModel
class+MainViewModel+@Inject+constructor(
++++...
)+:+ViewModel()+{|2177859|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/67256565/defaultactivityviewmodelfactory-not-found|1|https://dagger.dev/hilt/view-model.html^0|1|2|0|0|0|0|0|1B|9|2|13|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|D|3|E|5|F|7|1A|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|1B|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|1C|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|1D|8|@$A|1E|B|1F|O|P]]|9|@$A|1G|B|1H|1|1I]]|C|$]]|$1|Q|3|R|5|F|7|1J|8|@]|9|@]|C|$G|H]]|$1|S|3|T|5|6|7|1K|8|@]|9|@]|C|$]]|$1|U|3|V|5|F|7|1L|8|@]|9|@]|C|$G|H]]|$1|W|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]|14|$5|Z|10|11|C|$12|15]]]]

After <a href="https://stackoverflow.com/questions/67256565/defaultactivityviewmodelfactory-not-found">removing</a> the outdated library
<pre><code>implementation 'androidx.hilt:hilt-lifecycle-viewmodel:1.0.0-alpha03'
kapt 'androidx.hilt:hilt-compiler:1.0.0-alpha03'
</code></pre>
I got this error:
<pre><code>incompatible types: NonExistentClass cannot be converted to Annotation 
</code></pre>
Looking at <a href="https://dagger.dev/hilt/view-model.html" rel="nofollow noreferrer">https://dagger.dev/hilt/view-model.html</a> I changed in a <code>ViewModel</code>:
<pre><code>class MainViewModel @ViewModelInject constructor(
 ...
) : ViewModel() {
</code></pre>
to
<pre><code>@HiltViewModel
class MainViewModel @Inject constructor(
 ...
) : ViewModel() {
</code></pre>

blocks|key|2177889|text|对于所有像我这样的人来说，在这个话题上都犯了类似的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2177890|检查注释导入。|offset|length|style|BOLD|2177891|对我来说，问题是我的@MicronautTest注释和另一个测试一样，只是错误的一个。不知怎么的，intellij似乎认为导入是好的，而实际上却不是。|CODE|2177892|我有|2177893|import+io.micronaut.test.extensions.junit5.annotation.MicronautTest|2177894|但却需要最酷的那个。|2177895|import+io.micronaut.test.extensions.kotest.annotation.MicronautTest|2177896|kapt错误虽然在技术上是正确的，但却没有提供足够的信息。所以，只要检查进口和它们是否都是正确的。|2177897|entityMap^0|0|0|6|0|A|E|0|0|0|1V|0|0|0|1V|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|10|8|@$D|11|E|12|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|14|8|@$D|15|E|16|F|J]]|9|@]|A|$]]|$1|O|3|P|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|18|8|@$D|19|E|1A|F|J]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1B|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|V|$]]

For all those arriving like me on this topic with a similar error. 
Check your annotation imports. 
For me the problem was I had the <code>@MicronautTest</code> annotation same as another test just the wrong one. Somehow intellij seems to think the import is fine while it really is not.
I had 
<code>import io.micronaut.test.extensions.junit5.annotation.MicronautTest</code> 
yet needed the kotest one. 
<code>import io.micronaut.test.extensions.kotest.annotation.MicronautTest</code>
The kapt error is, while technically correct, quite uninformative.
So just check the imports and if they are all correct.

blocks|key|882125|text|ERROR+:+error.NonExistentClass|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|882126|这意味着提供依赖项存在问题(而不是依赖本身！)|unstyled|offset|length|style|BOLD|882127|有时候，由于提供者缺位，注释处理器(在本例中是Dagger)无法在第一个构建迭代中构建依赖关系图。|882128|例如:您正在将GlideApp作为参数传递到您的提供程序中，而GlideApp类尚未生成！因此，请注意您的提供者是否有NonExistentClass错误。|CODE|882129|entityMap|0|LINK|mutability|MUTABLE|url|https://bumptech.github.io/glide/doc/generatedapi.html#using-the-generated-api^0|0|4|5|E|3|0|0|1N|G|7|8|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|Y|8|@$G|Z|H|10|I|J]|$G|11|H|12|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|14|8|@$G|15|H|16|I|O]]|9|@$G|17|H|18|1|19]]|A|$]]|$1|P|3|-4|5|F|7|1A|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]]]

<pre><code>ERROR : error.NonExistentClass
</code></pre>
This means there is a problem with providing dependencies( and not the dependency itself!).
Sometimes annotation processor(in this case Dagger) is unable to build dependency graph on the first build iteration due to a provider absence.
For instance: You are passing <a href="https://bumptech.github.io/glide/doc/generatedapi.html#using-the-generated-api" rel="nofollow noreferrer">GlideApp</a> as a parameter in your provider while GlideApp class is not generated yet! So, watch out for your providers for <code>NonExistentClass</code> errors.

I'm using Dagger 2 and Kotlin for Android development.
My project is also a multi-module project.
My settings.gradle file is like this:

<pre><code>include :app
include :lib
</code></pre>

I'm also maintaining the lib module.

In the Dagger Files (for example in the component), I try to get the item from other module. For example:

<pre><code>@Component
interface AppComponent{
 fun getPresenter() : Presenter
}
</code></pre>

The Presenter object is defined in lib module. I was working in linux environment and I'm using Android Studio 3 preview canary 5. The code is working well and I am able to generate APK.

But my company wanted to generate the APK using stable version of Android Studio. I'm using Android Studio 2.3.3.

When compiling the Android Project, I encountered this error:

<pre><code>error: error.NonExistentClass
</code></pre>

The error appears when 

<pre><code>:app:kaptDebugKotlin 
</code></pre>

is performed and caused by the dagger class cannot found, the class is defined in the other project. What can be the possible workaround for this? Sorry for my bad English.

ERROR : error.NonExistentClass Kotlin In multi module Dagger project

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在使用Dagger 2和Kotlin开发Android。我的项目也是一个多模块的项目。我的settings.gradle文件是这样的：include :appinclude :lib我还在维护lib模块。在Dagger文件中(例如，在组件中)，我尝试从其他模块获取该项。例如：@Componentinterface ...

问错误:多模块匕首项目中的error.NonExistentClass Kotlin
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问错误:多模块匕首项目中的error.NonExistentClass KotlinEN