You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't see the same problem in our codebase. However, Dagger uses kotlinx-metadata to process Kotlin code in the kapt processor. In our project, compiling it with K2 KAPT enabled will produce NullPointer exception there. As Kotlin 2.0.0 comes with a new stable artifact for metadata processing, which makes it incompatible with the metadata generated with the K2/kapt. Resolving this requires an update to the newer artifact. I'm not so sure if the newer artifact will be backward compatible with K1-produced code though.
I have following configuration:
K2 Compiler
Kotlin 2.0.0-Beta1
Dagger 2.50
kotlin.experimental.tryK2=true
kapt.use.k2=true
Build failed with error:
Only Dagger uses kapt in my project.
Build is ok when kapt.use.k2=false.
The text was updated successfully, but these errors were encountered: