getting error while building ```> Task :common-...

# kotlin-native

[bipin]

getting error while building

> Task :common-ios:compileKonanKotlinMovieMakerIos_x64 FAILED
error: compilation failed: Expected data layout hash: -6046314956093995674 but actual is: 4180466727156567408

[bipin]

common-ios build.gradle

apply plugin: 'konan'

konan.targets = ['iphone_sim']

konanArtifacts {
    framework('KotlinMovieMaker') {
        enableMultiplatform true
        dependencies {
            artifactKotlinMovieMaker "com.russhwolf:multiplatform-settings-ios_x64:0.1-alpha3"
        }
    }
}

[russhwolf]

I haven’t updated that to 0.8 yet, so try using 0.7.1 if you aren’t already.

[bipin]

ext.kotlin_version = '1.2.50'
        ext.kotlin_native_version = '0.7'
        ext.gradle_build_tool_version = '3.1.3'

[bipin]

i am on 0.7 only

[russhwolf]

try 0.7.1

[russhwolf]

alternatively, are you missing the expectedBy dependency on your common module?

[bipin]

I have simple example, where having only 2 simple expectedBy classes

[russhwolf]

right. Not talking about classes. Your gradle file needs a dependencies block with an expectedBy dependency on your common module. See https://github.com/russhwolf/multiplatform-settings/blob/master/sample/shared/ios/build.gradle#L38

[bipin]

yeah, that i have defined

[russhwolf]

Ok. Not sure what’s happening at first glance, but will try to take a closer look later tonight or this weekend

[thevery]

I've got this error several times and fixed only by re-cloning project to another folder and removing ~/.konan

[sandwwraith]

This usually happens when you’re compiling your project with different version of compiler that library you depend on was compiled

[bipin]

yeah, Leonid is right, MultiplatformSettings lib using KN 0.7.1 and i was using 0.7,
Russell also pointed that before.
thanks guys

[thevery]

@sandwwraith is there any plans for binary compatibility between versions?

[sandwwraith]

I’m not aware of them, maybe @Pavel Punegov [JB] knows something

[russhwolf]

Presumably that will change by 1.0? Otherwise keeping dependency versions in-sync will become very painful.