https://android-developers.googleblog.com/2023/12/ksp2-preview-kotlin-k2-standalone.html

This might be more of a KSP issue, or a misunderstanding, but if I print out sourceSets.main.allSource.sourceDirectories, I get something like this:

project/src/main/resources, 
project/src/main/java, 
project/src/main/kotlin, 
project/build/generated/ksp/main/kotlin, 
project/build/generated/ksp/main/java

Notably missing is project/build/generated/ksp/main/resources. This messes with some other tools that use the sourceSet and expect to find the generated service files.

This apparently doesn't affect the actual Jar packaging, so I might just be using the wrong API here, but which one should I use?

How to reproduce

• fetch source

$ git clone https://github.com/ganadist/VersionCodeDemo -b autoservice_ksp_test test
$ cd test

• compile failed while using auto-service-ksp

$ ./gradlew :app:assembleDebug

> Task :app:kspBetaDebugKotlin FAILED
e: [ksp] test/app/src/main/java/com/example/myapplication/TestServiceImpl.java:5: No 'value' member value found!

• compile passed while using kapt

$ git checkout HEAD~1
$ ./gradlew :app:assembleDebug

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update kotlin monorepo to v2.0.10 (org.jetbrains.kotlin.jvm, org.jetbrains.kotlin:kotlin-compiler-embeddable)
• Update ksp to v2.0.10-1.0.24 (com.google.devtools.ksp, com.google.devtools.ksp:symbol-processing-api)
• Update dependency com.facebook:ktfmt to v0.51
• Update gradle/actions action to v4
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Requires google/ksp#431

Hi we have been actively using auto-service-ksp in our repo and found below issue:

The AutoService code generator doesn't support KSP very well (for example
The AutoService code generator doesn't process @autoservice in code-generated UiRegistry).

We believe below changes need to be made
https://kotlinlang.org/docs/ksp-multi-round.html#changes-to-your-processor

instead of returning an empty list here https://github.com/ZacSweers/auto-service-ksp/blob/main/processor/src/main/kotlin/dev/zacsweers/autoservice/ksp/AutoServiceSymbolProcessor.kt#L132

so it can support KSP correctly which is multi-round.

I'm not sure this bug is occured by auto-service-ksp or auto-service or kotlin.

I have multiple @AutoService annotated classes in multiple sourceset in same module. But services file contains lists of only one sourceset classes.

for example, I have files like this and all files have @AutoService(mypkg.MyTarget) annotions.

my_module/ src/ sandbox / mypkg / TargetA.kt
my_module/ src/ main / mypkg / MyTarget.kt
my_module/ src/ main / mypkg / TargetB.kt
my_module/ src/ main / mypkg / TargetC.kt

then, generated mypkg.MyTarget contains only TargetB , TargetC.

Is there any solution for this problem?

kotlin  = "1.6.10"
ksp = "1.6.10-1.0.2"
ksp-auto-service = "1.0.0"

Error,

> Cannot query the value of task ':kspKotlin' property 'classpathSnapshotProperties.classpathSnapshotDir' because it has no value available.

It seems like an issue with the old version of KSP this plugin depends on. Would it be possible to upgrade to the latest kotlin version?

Improvement description

The following code, rightfully, produces an error:

Code:

interface MyService

@AutoService() // note, no interfaces specified
class MyServiceImpl : MyService

Error

No service interfaces provided for element!

This error is quite confusing from the developer's perspective line of thought is as follows:

• Which element? Error points to line with class instead of annotation
• But my class inherits the desired interface!
• Sad wondering around the office

My company is actively migrating to Kotlin, had this thing in learning chats a couple of times already :)

Proposed solution

Add more clear message:

No service interfaces specified by @AutoService annotation!
You can provide them in annotation parameters: @AutoService(YourService::class)

This prevents usage in the following form:

compileOnly(libs.autoService.annotations)
ksp(libs.autoService.ksp)

as the testKsp configuration extends from the ksp configuration and thus the processor will run over the test sources where the annotation is not present.

Now an easy workaround is to testCompileOnly the annotation, but I don't have anything annotated in that source set so it's a bit weird.

I don't think this is a problem for the main source set either. If you omit the annotation dependency accidentally you would be unable to annotate any types.