I'm running into a strange issue with the 1.9.20 upgrade where my "*compileCommonMainKotlinMetadata"...

# multiplatform

[Rob Murdock]

I'm running into a strange issue with the 1.9.20 upgrade where my "*compileCommonMainKotlinMetadata"* task is failing due to not finding the kotlin standard library "map" collection extension. Has anyone else run into this or have a solution?

[Rob Murdock]

naturally, I have code in my commonMain that uses the map collection extension to, erm, map things to other things.

[ilya.gorbunov]

Just a guess, do you use mavenLocal repository in build scripts for getting dependencies?

[Rob Murdock]

I don’t believe so, but I am composing my build with multiple projects so I can build convention plugins. Would have have a similar effect?

[Rob Murdock]

I seem to keep alternating between having this issue and having a different issue with kotlin serialization and common code generating serializers for JavaScript. I’m guessing one of the issues is library misalignment, but that always leaves me with the other issue, which is similarly tough to resolve

[Rob Murdock]

See: https://kotlinlang.slack.com/archives/C7A1U5PTM/p1698928324720149

[ilya.gorbunov]

The version misalignment can also be the case. You can check which dependency versions are resolved in your project using Gradle build scan or by running dependencies Gradle task in the affected project.

[ilya.gorbunov]

The relevant dependency configurations for compileCommonMainKotlinMetadata would be metadataCommonMainCompileClasspath or metadataCompileClasspath

[Rob Murdock]

I'll take some more looking at it today