Incremental KSP fails in Java/Kotlin mixed module

[amandeepg]

If we have the following files (a Kotlin annotation, a Java annotated class, and a Kotlin constants file):

com.example.ann.MyAnn

annotation class MyAnn(val value: String)

com.example.JavaClass

public class JavaClass {
    @MyAnn(KotlinConsts.ACTION2)
    public void f() {
    }
}

com.example.KotlinConsts

class KotlinConsts {
    companion object {
        const val ACTION = "REPLACE"
        const val ACTION2 = "REPLACE"
    }
}

With a processor that looks for MyAnn and throws an error if the annotation value isn't "REPLACE":

resolver
    .getSymbolsWithAnnotation("com.example.ann.MyAnn")
    .filterIsInstance<KSFunctionDeclaration>()
    .forEach { func ->
        val arg = func.annotations.first().arguments.first().value.toString()
        if (!arg.startsWith("REPLACE"))
            throw IllegalStateException(arg)
    }

Then if we run the processor once, KSP runs fine. Then if we change @MyAnn(KotlinConsts.ACTION2) to @MyAnn(KotlinConsts.ACTION), and run KSP again, it will run under incremental mode, then we can no longer read the argument value, the condition isn't true, and we throw the IllegalStateException.

With the attached project:
playground3.zip

./gradlew  :workload:kspKotlin
# Edit JavaClass to reference KotlinConsts.ACTION instead
./gradlew  :workload:kspKotlin
# Observe that KSP was not able to read the annotation value

This prevents us from enabling incremental mode, which prevents us from using KSP as without incremental, our time in processing is higher than with Kapt where we can use incremental compilation.

[amandeepg]

Thanks! Confirmed that the fix works for the sample app submitted and the real application I discovered this in