Cannot inline bytecode built with JVM target 1.8 into bytecode that is being built with JVM target 1.6

H

38

786

When trying to run the Example CorDapp (GitHub CorDapp) via IntelliJ, I receive the following error:

Cannot inline bytecode built with JVM target 1.8 into bytecode that is being built with JVM target 1.6

How can I modify the IntelliJ settings so that all the bytecode is built with the same JVM target?

Hemicrania answered 26/2, 2018 at 12:41 Comment(3)

I was able to resolve this issue by adding this library to build.gradle dependencies { compile("org.jetbrains.kotlin:kotlin-stdlib-jdk8") } – Eula 30/10, 2018 at 15:44

@MunishChandel That is not sufficient. We must also do what the answer below suggests... – Stetson 6/9, 2019 at 14:17

Had the same error when specifying jvmTarget = "15" on Linux but the same project was working on Windows, both on IntelliJ 2020.3. Changed to jvmTarget = "14" and it worked on both. In either case there were no errors from the command line, only in IntelliJ. – Brandtr 2/12, 2020 at 21:7

H

308

You can fix this issue as follows:

Open the IntelliJ preferences
Go to Build, Execution, Deployment > Compiler > Kotlin Compiler BUT Other Settings > Kotlin compiler if Android Studio > 3.4
Change the Target JVM version to 1.8
Click Apply

Hemicrania answered 26/2, 2018 at 12:41 Comment(14)

I have this setting fixed to 1.8 already, yet I still see this error when stepping through breakpoints. I primarily see this when hitting vault queries. Any further suggestions? It seems this target JVM bit doesn't fix it entirely. – Laraelaraine 25/3, 2018 at 15:59

On your Project Structure, make sure you also change the Target platform to JVM 1.8 on your Kotlin Facet under the General tab. – Retouch 27/7, 2018 at 12:43

Would you know the instructions to do the same on eclipse? – Guardado 12/1, 2019 at 20:14

And after Apply restart IDE. – Soapsuds 10/2, 2019 at 15:42

This error can appear if there is an unresolved dependency! – Cytherea 14/2, 2019 at 8:42

For me the Kotlin Compiler settings were actually placed in Other Settings section. – Latria 3/7, 2019 at 13:12

If restarting after apply is not enough → Restart & Invalidate caches. – Submerse 4/8, 2019 at 19:40

Unfortunately that doesn't work if you have multiple modules. In that case you need to add ``` kotlinOptions { jvmTarget = "1.8" } ``` for every gradle in a module – Neldanelia 11/9, 2019 at 10:47

You should go to Kotlin Compiler – Stewardess 31/12, 2019 at 3:7

kotlinOptions { jvmTarget = "1.8" } – Chalybeate 5/2, 2020 at 13:15

I do not see General Tab or Build, Execution, Deployment on Android Studio though. – Eyeopener 21/3, 2020 at 5:57

As others have said, it was already set to 1.8 in the settings. Adding kotlinOptions { jvmTarget = "1.8" } in the build.gradle (Module: app) fixed it. – Martella 19/4, 2020 at 12:42

Doesn't work for me. Solved my problem with kotlinOptions – Backer 28/4, 2020 at 9:59

The above did not help me. I had to add the below to Module gradle.build file: ` tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompile).all { sourceCompatibility = JavaVersion.VERSION_1_8 targetCompatibility = JavaVersion.VERSION_1_8 kotlinOptions { jvmTarget = '1.8' apiVersion = '1.1' languageVersion = '1.1' } } ` from here: #44141576 – Plata 22/7, 2020 at 14:38

U

1541

app/build.gradle

android {
    ...
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    kotlinOptions {
        jvmTarget = JavaVersion.VERSION_1_8.toString()
    }
}

GL

Use Java 8 language features

Udine answered 11/7, 2019 at 19:21 Comment(12)

As of this date and Android Studio v3.5 this is the only solution that worked, after trying all the rest. Strangely enough setting the same value in Settings > Kotlin Compiler has no effect. – Onaonager 28/9, 2019 at 6:58

Just the kotlinOptions { jvmTarget = "1.8" } should suffice. – Sunbow 4/11, 2019 at 11:33

@Sunbow Some libraries need both options such as okhttp3:logging-interceptor to use OkHttpClient.Builder().addInterceptor – Udine 5/11, 2019 at 16:38

kotlinOptions { jvmTarget = "1.8" } – Chalybeate 5/2, 2020 at 13:14

Then should "invalidate cache and restart" – Wrier 22/2, 2020 at 17:12

I had already define the compileOption but not kotlinOption after define kotlinOption error gone. Its work for me. Thanks for sharing. – Chuipek 17/3, 2020 at 4:48

And what if this is not for android? Where do the compileOptions and kotlinOptions go? – Toponym 14/5, 2020 at 10:54

@PeterV.Mørch What context are you referring to? – Udine 14/5, 2020 at 20:14

Why some people wrap this kotlinOptions { } inside a tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompile).all { } ? – Beautiful 31/7, 2020 at 12:59

@LeonardoSibela In Gradle is that everything is executed against a Interface Project instance. These are tasks executed in the global instance of gradle, that is, at the level of the project module. So this configuration loses sense modularization since it configures all the existing build.gradle in the project. – Udine 31/7, 2020 at 14:23

If you're trying to inline 1.8 bytecode in another Gradle module, you should also put this code in another module too (not just app) – Shylashylock 6/10, 2020 at 16:2

Of course, the scope of the gradle is for the module unless you run tasks on the global gradle instance. – Udine 6/10, 2020 at 17:6

H

308

You can fix this issue as follows:

Open the IntelliJ preferences
Go to Build, Execution, Deployment > Compiler > Kotlin Compiler BUT Other Settings > Kotlin compiler if Android Studio > 3.4
Change the Target JVM version to 1.8
Click Apply