Open
Description
We have a custom processor for our FeatureToggles solution:
@FeatureToggle(key = "MOB_DEBUG_REQUEST_ENABLED", defaultsTo = BuildConfig.HTTP_REQUEST_DEBUGGING)With kapt, the value correctly read from Android's BuildConfig class (generated by buildConfigField).
With ksp, we get null instead on KSValueArgument[name = 'defaultsTo'].value.
I've seen a similar issue when there are compilations issues (like a missing class). I've not confirmed it, but I'm pretty sure that generated code from generate${variant}BuildConfig task's output is getting added as classpath for ksp task.