Ugi10/19/2020, 9:14 PM
, trying to resolve the dependancy for a sample project on
machine will fail because it's missing links to artifacts in latest module:
And vice versa. I haven't faced this behavior before, so is it something new, or am I doing something stupid because I'm tired?
No matching variant of com.ionspin.kotlin:multiplatform-crypto-libsodium-bindings:0.1.1-SNAPSHOT:20201019.205459-4 was found. The consumer was configured to find an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but: - Variant 'iosArm32-api' capability com.ionspin.kotlin:multiplatform-crypto-libsodium-bindings:0.1.1-SNAPSHOT: - Incompatible because this component declares a usage of 'kotlin-api' of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed an API of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' - Other compatible attribute: - Doesn't say anything about com.android.build.api.attributes.BuildTypeAttr (required 'debug')
common file when publishing to maven. And in any case ios/osx and windows targets wont run on linux so disabling them didn't bring any benefit.