ERROR : error.NonExistentClass Kotlin In multi module Dagger project

Question

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:

include :app
include :lib

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:

@Component
interface AppComponent{
    fun getPresenter() : Presenter
}

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:

error: error.NonExistentClass

The error appears when

:app:kaptDebugKotlin

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.

can you also post the output from `./gradlew build --info --stacktrace` — guenhter, Jul 14 '17 at 09:54

score 86 · Answer 1 · edited Oct 13 '20 at 16:35

86

Just add this to build gradle file to avoid the issues related NonExistentClass

kapt {
    correctErrorTypes true 
}

https://kotlinlang.org/docs/reference/kapt.html#non-existent-type-correction

edited Oct 13 '20 at 16:35

GoRoS

5,183
2
43
66

answered Apr 12 '19 at 07:51

seyfullah.bilgin

1,421
14
16

4

this helped me to find real issue. before adding this, the error was misleading – Fartab Oct 23 '19 at 18:15
5

this should be the accepted answer, as it takes you to the real issue. – Khurram Shahzad Jan 10 '20 at 18:48
1

thanks, you're a lifesaver. my problems also arised regarding the android studio forcing to use androidx when `ViewBinding` – mochadwi Feb 26 '20 at 11:03
Shouldn't it be `correctErrorTypes = true` ? – EndermanAPM Aug 05 '21 at 13:49
1

On a kt gradle file it was failing to build for me without the = – EndermanAPM Aug 10 '21 at 10:57

Iman Akbari · Accepted Answer · 2017-07-29T10:05:44.593

The Root Cause

Basically, there's not much that can be done to fix this when using kapt. To quote this link that tackles the same problem in another library that uses pre-processors (OrmaDatabase):

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

How to fix it (the workaround)

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

kapt libs.daggerCompiler

to

annotationProcessor libs.daggerCompiler

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

You can also run `./gradlew :app:compileDebugJavaWithJavac --stacktrace` to find out the source of the error. — starkej2, Dec 12 '17 at 21:54

score 8 · Answer 3 · answered Aug 27 '18 at 11:18

8

I had a very similar situation with a NonExistentClass 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:

implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$rootProject.kotlinVersion"

answered Aug 27 '18 at 11:18

GoRoS

5,183
2
43
66

1

Had nearly the same - in my case I forgot to add `kotlin-android` plugin to module's build.gradle. – Viacheslav Jul 11 '19 at 11:16

score 6 · Answer 4 · answered Dec 11 '17 at 00:50

6

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.

answered Dec 11 '17 at 00:50

Andras Kloczl

8,415
2
21
23

Using annotationProcessor showed the problem to me. Thanks! – Tgo1014 Feb 11 '20 at 10:23

score 5 · Answer 5 · answered May 24 '21 at 15:23

5

After removing the outdated library

implementation 'androidx.hilt:hilt-lifecycle-viewmodel:1.0.0-alpha03'
kapt 'androidx.hilt:hilt-compiler:1.0.0-alpha03'

I got this error:

incompatible types: NonExistentClass cannot be converted to Annotation

Looking at https://dagger.dev/hilt/view-model.html I changed in a ViewModel:

class MainViewModel @ViewModelInject constructor(
    ...
) : ViewModel() {

to

@HiltViewModel
class MainViewModel @Inject constructor(
    ...
) : ViewModel() {

answered May 24 '21 at 15:23

CoolMind

26,736
15
188
224

i am getting unresolved reference on @Inject , does i miss something ? – iamkdblue Jul 02 '21 at 01:51
@Kuldeepmourya, maybe you should rebuild the project. Or check providers maybe. – CoolMind Jul 02 '21 at 06:22

score 4 · Answer 6 · answered May 25 '19 at 10:53

4

In my case, I had @Nullable annotation from support-annotations while I had removed it in order to migrate to AndroidX.
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.

answered May 25 '19 at 10:53

Mahdi-Malv

16,677
10
70
117

This was actually my problem. Thanks! – dipdipdip Nov 06 '19 at 19:21
1

Replacing all imports from `org.jetbrains.annotations.Nullable` to `androidx.annotation.Nullable` fixed the issue for me – Vaibhav Jani Nov 14 '20 at 06:14

score 2 · Answer 7 · edited Oct 13 '20 at 16:35

2

I've found if you're using

kapt {
    generateStubs = true
}

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

edited Oct 13 '20 at 16:35

GoRoS

5,183
2
43
66

answered Oct 07 '17 at 09:17

ngatirauks

779
8
18

score 1 · Answer 8 · answered Jul 14 '17 at 12:51

1

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

./gradlew clean

answered Jul 14 '17 at 12:51

ArtKorchagin

4,801
13
42
58

Plus Invalid Cache and Restart did it for me. – chrjs Apr 11 '19 at 10:00
as stated on youtrack.jetbrains issue, we've to delete the `./gradle/caches`: https://youtrack.jetbrains.com/issue/KT-35554#focus=streamItem-27-3881549.0-0 – mochadwi Feb 26 '20 at 09:19
This worked great for me when nothing else did! – waseefakhtar Jan 19 '22 at 16:11

score 1 · Answer 9 · answered Jul 12 '19 at 10:11

1

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.

answered Jul 12 '19 at 10:11

alexy

464
5
6

score 1 · Answer 10 · answered Aug 20 '19 at 09:50

1

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

answered Aug 20 '19 at 09:50

Anuj Garg

959
10
12

score 1 · Answer 11 · answered Jun 16 '21 at 13:10

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 @MicronautTest 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
import io.micronaut.test.extensions.junit5.annotation.MicronautTest
yet needed the kotest one.
import io.micronaut.test.extensions.kotest.annotation.MicronautTest

The kapt error is, while technically correct, quite uninformative. So just check the imports and if they are all correct.

score 1 · Answer 12 · answered Oct 13 '21 at 07:42

ERROR : error.NonExistentClass

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 GlideApp as a parameter in your provider while GlideApp class is not generated yet! So, watch out for your providers for NonExistentClass errors.

score 1 · Answer 13 · answered Jun 16 '23 at 06:34

1

Its a compilation sync issue.

Do

./gradlew clean build

or

invalidate cache and restart

answered Jun 16 '23 at 06:34

shubham chouhan

580
7
8

score 0 · Answer 14 · answered Dec 20 '18 at 09:20

0

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.

answered Dec 20 '18 at 09:20

mjurekov

37
3

score 0 · Answer 15 · answered May 03 '19 at 16:47

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.

-    androidTestCompile "org.mockito:mockito-android:2.7.21" // remove this
+    androidTestCompile "org.mockito:mockito-android:2.+"    // add this

score 0 · Answer 16 · answered May 04 '19 at 10:38

0

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

My Case:

Our project had few modules in it, lets call one of them myModuleProject. 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 ':myModuleProject:kaptDebugKotlin' and with long list of errors such as

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()

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

android.databinding.enableV2=true
android.useAndroidX=true
android.enableJetifier=true

answered May 04 '19 at 10:38

Vilen

5,061
3
28
39

Where would I put that in a module, exactly? – bernardo.g May 31 '19 at 17:42
in module's `gradle.properties` file – Vilen Jun 03 '19 at 06:02
Mmm, there's no gradle.properties file in my modules, only the top-level one... Any idea why that is? – bernardo.g Jun 03 '19 at 13:20
I am not sure why don't you have gradle.properties file but you can add it, it is just a test file with .properties extension – Vilen Jun 04 '19 at 17:41
*text file .properties – Vilen Jun 13 '19 at 05:22

score 0 · Answer 17 · answered Jun 14 '19 at 08:50

0

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

import foo.*  // class foo.Abc
import bar.*  // annotation bar.Abc

@Abc
class Xyz { ... }

answered Jun 14 '19 at 08:50

Wang Qian

51
4

score 0 · Answer 18 · answered Jul 26 '20 at 15:56

I had a project with Dagger injecting something into Presenters At one moment I got a persistent "NonExistentClass.java:3: error: error.NonExistentClass must be INTERFACE" 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.

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 {
Search at the compiled by kapt build files in /home/alex/AndroidProvects/TopProject/app/build/tmp/kapt3/stubs/onlineDebug/app for "NonExistentClass" string
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)

score 0 · Answer 19 · answered May 20 '21 at 21:14

I had similar issues with dagger. Adding the following helped solve it :

// 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')

ERROR : error.NonExistentClass Kotlin In multi module Dagger project

19 Answers19

The Root Cause

How to fix it (the workaround)

My Case:

Linked