I'm upgrading to compose `alpha12` . Last warning I have is `Flag is not supported by this version ...

# compose

[BenjO]

I'm upgrading to compose alpha12 .
Last warning I have is Flag is not supported by this version of the compiler: -Xallow-jvm-ir-dependencies .
Does anyone know why ? 🙏

[BenjO]

I use Kotlin plugin version : 203-1.4.30-RC-AS6682.9

[BenjO]

I'm using kotlinOptions.allWarningsAsErrors = true in my project, so this warning fails the build right now 😕 warning shows up even after I removed the entry from the freeCompilerArgs

[jim]

I believe this is added by AGP, filed a bug: https://issuetracker.google.com/issues/179990559

[Klaas Kabini]

I am also experience this error during build

[allan.conda]

link above is for Google only, btw ^

[BenjO]

yes you're right.
@jim , is AGP bug tracker different than https://issuetracker.google.com ?

[jim]

ugg, no, just all our internal URLs are different from the public URLs for no apparent reason, and sometimes we forget to change them before pasting into slack. If you ever see one of our internal URLs, you can just grab the bug number off the end of the URL and create your own issuetracker compatible URL. So in this case, that would be: https://issuetracker.google.com/issues/179990559

I'll go ahead and edit my previous comment to make the URL clickable for you all.

[BenjO]

I got an access denied 🤔

[allan.conda]

Yeah some compose categories are not accessible outside also. Found out before when I tried to file a bug.

[jim]

Well, the TLDR is that the fix has been merged into master and is currently scheduled to go out as part of 2020.3.1 Canary 8 [20020.3.1.8]/AGP 7.0-alpha08.

[BenjO]

that's good to hear !

[BenjO]

@jim I just ugraded to 2020.3.1 / AGP alpha08 and I still got the same warning

[jim]

@BenjO And you've double-checked that you're not adding the flag (-Xallow-jvm-ir-dependencies) manually in your build.gradle files?

[BenjO]

well, I set this flag because of compose (https://developer.android.com/jetpack/androidx/releases/compose-foundation#declaring_dependencies)
Because I use it in conjunction with kotlinOptions.allWarningsAsErrors = true it breaks the build.

After invalidating the cache and a restart, I still have two warnings but build is working

[jim]

Ah, those docs just need to be updated, you shouldn't need to set that flag anymore

[BenjO]

Ah! Meanwhile I managed to make them disappear 🤔
I was using tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompile).all instead of `tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompile).configureEach``

[BenjO]

Anyway 🙏 @jim

[BenjO]

Nice, docs are up-to-date now !

[jim]

😇

[jim]

They're up-to-date because you identified and raised the issue here. Thanks for bringing it up.

[BenjO]

It looks like the kotlinCompilerVersion has been deprecated. It is still visible in the official docs. If not mandatory anymore, it may be easier to remove the line. It's less setup for the devs.

composeOptions {
        kotlinCompilerVersion "1.4.30"
}

[Klaas Kabini]

The docs need to be updated.