I think this issue regressed in 1.0.26, it reprodu...
# kspz
Zac Sweers
10/24/2024, 4:53 PMI think this issue regressed in 1.0.26, it reproduces 100% in our project now and originates from KSP's own internal code rather than any custom processors doing their own caching
https://github.com/google/ksp/issues/1854
n
Nicklas Jensen
11/05/2024, 2:49 AMI noticed the same on a project of mine. I instruct users of Mockative to disable incremental processing if they observe this issue:
Copy code
ksp.incremental=false