A modern programming language that makes developers happier.

kotlinlang

wanted to nudge this issue - <https://github.com/google/ksp/issues/1789#issuecomment-2860100164>

With AGP 8.10.0, we're more or less not able to apply the KSP plugin on-demand with our convention plugin anymore due to its odd interaction with AGP's lifecycle

It should be easy to unconditionally register the tasks and make them no-ops, but I'm not sure about these without further evaluation:
1. performance impact
2. any other side-effects
On the other hand, may I know why, in your use case, ksp needs to be applied that late?

our convention plugin needs to evaluate our extension first to determine if KSP is needed

here's our logic <https://github.com/slackhq/foundry/blob/bf589f25773aaa5a2e6a3da659e3a3ffff14277c/platforms/gradle/foundry-gradle-plugin/src/main/kotlin/foundry/gradle/FoundryExtension.kt#L150|https://github.com/slackhq/foundry/blob/bf589f25773aaa5a2e6a3da659e3a3ffff14277c/p[…]radle-plugin/src/main/kotlin/foundry/gradle/FoundryExtension.kt>

I consulted a Gradle expert and ksp should not resolve configuration in configuration / evaluation time. That means tasks can only be registered unconditionally anyways. I'll fix it in KSP's side.