I was able to reproduce the `Unresolved reference`...
# kotlin-inject
s
I was able to reproduce the
Unresolved reference
bug in your sample: https://github.com/evant/kotlin-inject-samples/pull/3
e
Alright looked into this, it is in fact a bug with ksp. But good news, checked out the latest main and it's fixed there! So we just need to wait for another release. Will put up a pr for a fix for the confusing error message though.
s
Oh nice! Is it possible for me to use a newer version of KSP than the one being used by kotlin-inject?
e
yep, all new versions of KSP are backwards compatible. Which is a good thing, otherwise we'd have to publish a new lib release with every kotlin version change.
s
awesome, let me try it out and report back
e
lmk if you see anything different, but ksp 1.0.1-RC seems to be working for me!
s
what were your steps for updating to 1.0.1-RC? I tried bumping my version but I'm running into:
Copy code
> Could not create task ':common:kspDebugKotlinAndroid'.
   > 'org.jetbrains.kotlin.gradle.tasks.KotlinCompile$ClasspathSnapshotProperties com.google.devtools.ksp.gradle.KspTaskJvm.getClasspathSnapshotProperties()'
I wonder if it's because it's dependent on kotlin 1.6.0?
e
hm, didn't see that error exactly but yes you need kotlin 1.6.0-RC
s
that sucks considering how painful it is to update kotlin version in multiplatform. let me file a request to ksp to publish bugfixes with kotlin 1.5.31.
e
As an aside, curious what dep issues you run into on multiplatform these days. It used to be you had to publish your dependencies lockstep with kotlin releases but that hasn't seemed to be the case with the last several versions.
s
ooh, are new kotlin native released no longer abi incompatible with old versions?
e
I think so, it least it's worked for me