Wondering if anyone can enlighten me to what might...
# community-support
t
Wondering if anyone can enlighten me to what might be causing an issue with a gradle plugin that started failing to compile when updating the KSP plugin.
Copy code
e: file:[....]/ScreenshotPlugin.kt:62:69 None of the following functions can be called with the arguments supplied: 	
public constructor File(p0: File!, p1: String!) defined in java.io.File	
private constructor File(p0: String!, p1: File!) defined in java.io.File	
private constructor File(p0: String!, p1: Int) defined in java.io.File	
public constructor File(p0: String!, p1: String!) defined in java.io.File
change is literally just the ksp dep and about as minimal as possible. both versions have no dependencies so not sure if I should be more suspect of some gradle behavior I don't understand or if I should report this to the KSP project.
v
What is the mentioned line in the screenshot plugin?
t
file constructors inside of some maps from outputs of the kspTask.
its a little bit weird. we generate some tests from the main srcSet ksp task then copy them over to a directory that feeds into the test srcSet.
e
as you can see the type of
destination
changed, so your code must change too
👆 1
you should probably define a separate output directory for your generated tests, and pass the path as an input to your processor
t
oh duh. good eye. thank you
you should probably define a separate output directory for your generated tests, and pass the path as an input to your processor
I want to say the issue we hit with that approach was how the writer API in KSP is setup. IIRC you end up with some different problems in correctness if you write outputs using anything other than their api? Not totally sure, its been many months since we added this plugin and I didn't author it myself only advised from a distance.
if AGP ever makes their preview snapshot plugin not terrible for the image diffing configuration I'll be able to just nuke all this