[KSP2] @Inject fields may not be final - androidInjector in dagger.android.DaggerApplication

[SimonMarquis]

• Dagger: 2.55 (latest)
• KSP: 2.1.10-1.0.30 (latest stable)
• ksp.useKSP2=true in gradle.properties

Compiling an Android app with this configuration, and the following Application class (we still rely on the DaggerApplication for legacy dagger graph):

@HiltAndroidApp
class MyApp : DaggerApplication()

leads to the following error:

> Task :app:kspReleaseKotlin
e: [ksp] @Inject fields may not be final - androidInjector in dagger.android.DaggerApplication

dagger/java/dagger/android/DaggerApplication.java

Line 33 in 3309ac2

@Inject volatile DispatchingAndroidInjector<Object> androidInjector;

[bcorso]

This issue seems like a bug in KSP2 or XProcessing library, as Dagger just looks for the final modifier to report this error.

1. Which version of Kotlin are you using?
2. Does this issue happen with ksp.useKSP2=false?
3. Does this issue happen with previous versions of Kotlin/KSP (e.g. Kotlin 2.0.21 and KSP 2.0.21-1.0.28)?

---

Note that KSP2 is not officially supported with Dagger yet. We're currently in the process of trying to support KSP2; however, there are still many issues/discrepancies with KSP2 compared to KSP1 so we are working with KSP team to address those issues.

I also realize this isn't a great place for users because KSP1 is not really guaranteed to work with Kotlin 2.1.x, so getting KSP2 support enabled is currently one of our top priorities.

(see also the discussion here: #4505 (comment)).

[SimonMarquis]

1. Which version of Kotlin are you using?

Sorry for not mentioning it, but since we are using KSP 2.1.10-1.0.30, we are relying on Kotlin 2.1.10

2. Does this issue happen with ksp.useKSP2=false?

No, only with ksp.useKSP2=true

3. Does this issue happen with previous versions of Kotlin/KSP

No idea, I'll try next week some other versions and will report back to you. 🫡

Note that KSP2 is not officially supported with Dagger yet.

I'm well aware, that's why I explicitly mentioned KSP2. I reported it to avoid "re-discovering" this issue when the 1st KSP2-compatible release becomes stable. I'd rather not have to wait for a patch/release cycle 😜

[bcorso]

Looks like this is a known regression in KSP 1.0.30: google/ksp#2346

Looks like it is slated to be fixed in 1.0.31 or you can try to downgrade to 1.0.29.

I'll close this bug since there's nothing to do on our side.