It looks like kapt/ksp have biggest impact on incremental compilation times in our Android project. Even if I change a little detail in a class (non-abi change) that doesn’t even contain any Hilt/dagger annotations and is hidden behind interface, I still see kapt task taking significant time. I suppose a lot of stubs are being regenerated which has further impact on compilation times. Is there a way to know what prevented the kapt task from considering being up-to-date?

Easier way would be to inspect Gradle build scan and check why kapt tasks were considered as non UP-TO-DATE