With the changes made to kapt in 1.3.31, kotlin do...

# android

[tevjef]

With the changes made to kapt in 1.3.31, kotlin does some aggressive caching to decrease incremental built times. Unfortunately, some annotation processors and kapt don’t work well together and the cache is not properly invalidated in some conditions.
- Deleted classes with @Inject may still have code generated for them.
- Moved classes with @Inject may still have code generated in the old location.

This behavior is enabled by default in Kotlin 1.3.31. Is there something I need to configure kapt to ensure the cache is properly invalidated?
This is causing some issues for my team, especially when we switch between branches.

Thank you! I’ve beed getting sub 1 min incrementally builds for the first time in months.

[gildor]

This is probably problem of annotation processor, I saw discussion somewhere about this issue in dagger

[gildor]

also, are you sure that you enabled incremental Dagger build?

[tevjef]

I created an issue here: https://youtrack.jetbrains.com/issue/KT-31322