Kotlin kapt "cannot find symbol" for generated code in CI
kapt compiles generated Java stubs and a referenced generated symbol does not exist. Either generation failed earlier or the reference name is wrong.
What this error means
The build fails in a kapt task with error: cannot find symbol naming a generated class like DaggerAppComponent. It is deterministic.
gradle
> Task :app:kaptDebugKotlin FAILED
error: cannot find symbol
DaggerAppComponent.create().inject(this)
symbol: class DaggerAppComponentCommon causes
Generation failed upstream
An earlier processor error means the generated class was never produced, so the reference cannot resolve.
Processor not declared with kapt
The annotation library is present but the matching processor was not added via kapt(...), so nothing generates.
Stale generated sources cached
A cached build keeps generated output from before a rename, so the new name is missing.
How to fix it
Declare the processor with kapt
build.gradle.kts
dependencies {
implementation("com.google.dagger:dagger:2.51")
kapt("com.google.dagger:dagger-compiler:2.51")
}Resolve the real generation error first
- Scroll above the cannot-find-symbol line to the actual processor error.
- Fix that error so the class generates.
- Run a clean build to drop stale generated sources.
CI step
./gradlew clean :app:kaptDebugKotlinHow to prevent it
- Declare every processor with kapt or ksp.
- Fix upstream processor errors before chasing missing symbols.
- Clean generated sources after renames.
Related guides
Kotlin KSP "symbol processing failed" in CIFix Kotlin Symbol Processing (KSP) "symbol processing failed" errors in Gradle CI - a KSP processor crashed o…
Kotlin "Unresolved reference" variant in CIFix Kotlin "Unresolved reference" errors in Gradle CI for member access and extension functions - the named s…
Kotlin "compiler daemon terminated" in CIFix the "Kotlin compile daemon terminated" / disconnected error in Gradle CI when the Kotlin daemon dies mid-…