Cannot inline bytecode built with JVM target 11 into bytecode that is being built with JVM target 1.8. Please specify proper '-jvm-target' option about compose-destinations HOT 11 CLOSED

Hi!
Thanks for a reply.
Sadly targeting java 11 does not helped. I got same error.

from compose-destinations.

Hello! I stumbled upon the same issue and after switching to java 11 I had to invalidate the caches of Android Studio, that fixed it.

from compose-destinations.

Hello! I stumbled upon the same issue and after switching to java 11 I had to invalidate the caches of Android Studio, that fixed it.

Thank you! Now it works perfectly! :)

from compose-destinations.

Are you using desugaring? It seems to be related.
To be completely honest, I am not sure I fully understand all the implications here, but I was able to reproduce the reported issue and then I was able to fix it in the library.

from compose-destinations.

Hi!

Hmmm 🤔
I need to take some time to analyse this properly, I have never seen it before.
I'll mark it also for v2.
Until then, try targetting java 11, that probably fixes it.

from compose-destinations.

It seems like according to: https://developer.android.com/build/jdks#compileSdk java 11 is only supported on Android api 32 and above, we need to support from api level 21... would it be possible to use

    sourceCompatibility = JavaVersion.VERSION_1_8
    targetCompatibility = JavaVersion.VERSION_1_8

to compile this library?

from compose-destinations.

We are using this library at work and our min sdk is 24. We’re also targeting Java 11 with no issue.

I will be checking this later on, but for now I’m not considering this urgent since I believe it works with all min sdk that compose also requires.

from compose-destinations.

But @dave08 if you find any issue with your min sdk please do let me know 🙂

from compose-destinations.

@raamcosta Compose supports from sdk 21...

from compose-destinations.

Hi guys!

After some tests I did find that my understanding of these jvm targets was off, apologies 🙏

1.9.56 is cooking where this should be fixed. Thank you for reporting 🙇

from compose-destinations.

@raamcosta
Can you share your analysis of JVM 17
We are using following configuration in our app

compileOptions {
sourceCompatibility JavaVersion.VERSION_17
targetCompatibility JavaVersion.VERSION_17
}
kotlinOptions {
jvmTarget = '17'
}

And our app support is 21 & above. And the app seems to be working fine.

from compose-destinations.