Thread
#compose
    BenjO

    BenjO

    1 year ago
    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 ? 🙏
    I use Kotlin plugin version : 203-1.4.30-RC-AS6682.9
    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

    jim

    1 year ago
    Klaas Kabini

    Klaas Kabini

    1 year ago
    I am also experience this error during build
    a

    allan.conda

    1 year ago
    link above is for Google only, btw ^
    BenjO

    BenjO

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

    jim

    1 year ago
    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

    BenjO

    1 year ago
    I got an access denied 🤔
    a

    allan.conda

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

    jim

    1 year ago
    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

    BenjO

    1 year ago
    that's good to hear !
    @jim I just ugraded to 2020.3.1 / AGP alpha08 and I still got the same warning
    jim

    jim

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

    BenjO

    1 year ago
    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

    jim

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

    BenjO

    1 year ago
    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``
    Anyway :thank-you: @jim
    Nice, docs are up-to-date now !
    jim

    jim

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

    BenjO

    1 year ago
    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

    Klaas Kabini

    1 year ago
    The docs need to be updated.