I’m having an issue where specific KSP processor can’t resolve declarations generated on previous ro...

# ksp

[ilyagulya]

I’m having an issue where specific KSP processor can’t resolve declarations generated on previous round by another KSP processor (i’m sure that all sources are accessible at the moment of processor being run. I’ve even added a special step to skip one round to be sure that generated files are accessible).
I’m using resolver.getDeclarationsFromPackage to access those declarations.
I’ve started debugging and found out that inside resolver.getDeclarationsFromPackage there’s a code

module.getPackage(FqName(packageName))
      .memberScope.getContributedDescriptors(noPackageFilter)

which returns a list without my generated sources either.
I can see generated sources inside the build/generated/ksp/debug/ folder.
On the screenshot there’s 3 generated files, but only 2 of them are accessible (you can see this on screenshots).
How should I debug this issue?
What could be possible cause?

[ilyagulya]

Hmm, seems that on some rounds of processing this generated declarations are visible. Will debug further 🙂

[ilyagulya]

Ok, for some reason when I skip not one, but 2 rounds, these declarations are available and build succeeds 😅

[ilyagulya]

@Zac Sweers btw, this is from your z/kspMerging branch.
I’ve made several fixes, is it okay if I will post a link to them in your PR? 🙂

[Zac Sweers]

in my fork or on square/anvil?

[Zac Sweers]

if it’s in my fork then PR definitely welcome. The square/anvil branch is old though

[ilyagulya]

on square/anvil
there’s a newer version? 😅

[ilyagulya]

ok, I’ll take a look 😄