I'm having the same error after upgrading several ...

# getting-started

[zt]

I'm having the same error after upgrading several of my projects to kotlin 2.0.0 for all native targets:

w: KLIB resolver: The same 'unique_name=org.jetbrains.kotlinx:atomicfu' found in more than one library: /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/atomicfu-linuxx64/0.20.2/6ad420ede07f27d1faff29de57851048afe77474/atomicfu.klib, /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/atomicfu-linuxx64/0.23.1/8c5db273962e5bee0c7cafb5c2e77aba595e0a3c/atomicfu.klib
w: KLIB resolver: The same 'unique_name=org.jetbrains.kotlinx:atomicfu-cinterop-interop' found in more than one library: /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/atomicfu-linuxx64/0.20.2/8cda96bf87ece8377d6307f8145182e9c46d226c/atomicfu-cinterop-interop.klib, /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/atomicfu-linuxx64/0.23.1/d44a87a9f79f578e7b36a853477cb61e794d6b74/atomicfu-cinterop-interop.klib
w: KLIB resolver: The same 'unique_name=org.jetbrains.kotlinx:kotlinx-coroutines-core' found in more than one library: /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-core-linuxx64/1.7.1/b465f13ffe74e2d4d2b8448839e2ee6275f67fda/kotlinx-coroutines-core.klib, /home/nick/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-core-linuxx64/1.8.1/6cd5eda771c30c4e76ee7bc56f43051836e51b4d/kotlinx-coroutines-core.klib

[dmitriy.novozhilov]

cc @dmitriy.dolovov

[dmitriy.dolovov]

This is a strange situation: The same library is passed twice to the compiler input:
• org.jetbrains.kotlinx/atomicfu-linuxx64/0.20.2
• org.jetbrains.kotlinx/atomicfu-linuxx64/0.23.1
@zt Do you have a reproducer? If yes, could you file a ticket for us to https://youtrack.jetbrains.com/issues/KT?

[zt]

I think I've slightly narrowed it down. I'm using https://github.com/Kotlin/binary-compatibility-validator/releases 0.14.0 in my project
The error seems to only occur whenever the existing api dump doesnt match the current code api, except its not every time I run a check. Now I'm struggling to produce the error