Hi! I'm facing an issue with a KMP project that ha...

# gradle

[Bernd Prünster]

Hi!
I'm facing an issue with a KMP project that has JVM and Android targets:
• The JVM target is build for Java 17, the Android target is built for Java 1.8. in the common code
• There's an inline function delegating to an expect/actual function.
• The expect/actual function has implementations for the JVM and for Android (separate targets, separate source sets, separate JVM targets)
So far, so good. However, when trying to call this inline function from another project's common source set (which also has discrete JVM and Android targets), things go south: For whatever reason, the Andoid target resolves the inline function to the JVM target. Rightfully, the compiler complains that JVM 17 bytecode cannot be inlined into JVM 1-8 bytecode.

While I am pretty sure that this is a tooling bug (it would not be the first we've encountered), I'd like to get some input before reporting and double-check that its not some miswired project setup on our end.

[ephemient]

did you publish the Android variant(s)? https://kotlinlang.slack.com/archives/C19FD9681/p1707157045959099?thread_ts=1707149614.275589&cid=C19FD9681

[Bernd Prünster]

yup. everything's in maven central. to get the consuming library published, we worked-around it, by axplicitly calling the non-inline variant of the funcion: https://github.com/a-sit-plus/vck/commit/393c6d3954772f40e5a1a433192144ae5bc97c0c#diff-40089862ddbd341db4d8ccd456[…]00d457d46cae76b2010bdf03e331L183

[Bernd Prünster]

wait a second… a merge might have gone wrong. thanks for the hint! I'll report back

[Bernd Prünster]

indeed, a module was missing it. rebuilding everything will take about 20 minutes. I'll report back.

[Bernd Prünster]

Indeed, one module was missing it! Thank you very much!