The error is even triggered when I depend on the l...

# multiplatform

[audax]

The error is even triggered when I depend on the library jar and not the module. 😐

[audax]

The shared library and the backend code must be in different projects, it's not enough to just depend on the jar.

[audax]

This is super ugly…

[darkmoon_uk]

Maybe Gradle Composite can save you?

[darkmoon_uk]

Keep your KMP library in a separate 'library project' and Gradle Composite it in. I believe the type resolution goes through a different pathway in this arrangement that might resolve the issue.

[audax]

Oh, that's indeed worth a try, thanks!

[darkmoon_uk]

Keen to know how it works out!

More than casually interested - I've also hit issues with typealias-ing in the recent times after 2.0, and am a heavy user of Gradle Composite

[audax]

The bug surfaces as soon as I activate the composite build. 😭

[audax]

But I'll use this technique to integrate the publish-step of the shared module into the main projects build.

[audax]

Even marking the whole module folder as excluded doesn't work.

[audax]

Well, now I use the composite build with a commandline argument to include the publish-task of the shared module into the main build. At least the CI-build doesn't have to deal with that stuff 😄