Status Update
Comments
sg...@google.com <sg...@google.com> #2
Yigit, I haven't had time to try reproducing yet, but they have a github link which is nice. What's weird though is I don't think anything has changed recently at all, but maybe you're aware? Although, looking at the callstack, it may be an AGP issue? If it looks like that to you too, bounce it back to me.
OP: Was this a regression? And just to make sure, when you say "run ./gradlew help
", you're seeing this from the command line? Or from within Studio?
sg...@google.com <sg...@google.com> #3
I'm seeing this from command line.
Yes this seems to be a regression starting from 7.0.0-alpha10.
Note that the project I linked doesn't use databinding at all, enabling the build config flag is all that's needed to reproduce this.
sg...@google.com <sg...@google.com> #4
Thanks for the quick reply. I have a short open window right now so I'll try to repro and see if I can figure out which component this is best for.
sg...@google.com <sg...@google.com> #5
I can repro what OP is seeing. It may be tempting to move this to the data binding component but this seems more like an AGP change. I don't believe the data binding compiler has been changed recently, around the time AGP 7.0.0-alpha10 went out.
ap...@google.com <ap...@google.com> #6
Also, slightly more direct steps (although it amounts to the same thing as what's in
- Sync the github project somewhere (
git clone https://github.com/ReactiveCircus/streamlined.git
) - Double check everything's working as expected (
./gradlew help
should work) - Edit
app/build.gradle.kts
: Search forbuildFeatures
and adddataBinding = true
as the first entry, abovebuildConfig
- Now, things are expected to break (
./gradlew help
should throw an exception) - Edit
buildSrc/src/main/kotlin/io/github/reactivecircus/streamlined/Dependencies.kt
: change the AGP version to7.0.0-alpha09
- Now, things are expected to work again(
./gradle help
should work)
ap...@google.com <ap...@google.com> #7
yea this seems unrelated to data binding as we didn't change data binding itself
There were some resource related changes so cc'ing Iza in case they might be related but i don't think so. This seems like a lifecycle issue.
ap...@google.com <ap...@google.com> #8
I'll look more into this, thanks for the detailed description and repro case!
ap...@google.com <ap...@google.com> #9
This affects even 1.50-M1 kotlin, and the code resolving the attributes is here:
As a workaround to get data binding working, I'll add a new task that merges dependencies R.txt files into one, and then pass that single file to kapt/db. So while the incorrect resolving will still be there while jetbrains fixes this issue, it will allow the non-transitive R + data binding builds to succeed.
ap...@google.com <ap...@google.com> #10
nice find!
There is actually another issue about incremental compilation, do you think they might be related to the other issue you've mentioned?
ap...@google.com <ap...@google.com> #11
ap...@google.com <ap...@google.com> #12
ap...@google.com <ap...@google.com> #13
This affects even 1.50-M1 kotlin, and the code resolving the attributes is here:
https://github.com/JetBrains/kotlin/blob/master/libraries/tools/kotlin-gradle-plugin/src/main/kotlin/org/jetbrains/kotlin/gradle/internal/kapt/Kapt3KotlinGradleSubplugin.kt#L354
This is similar to/the same as
Regarding
ap...@google.com <ap...@google.com> #14
ap...@google.com <ap...@google.com> #15
Thanks! Do we know if this is going to be included in the next canary (or one after that)? It's been blocking us from updating AGP / Studio for 4 releases now so I'd really love to get back to the bleeding edge soon:)
ap...@google.com <ap...@google.com> #16
sg...@google.com <sg...@google.com> #17
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Chipmunk Canary 2 (2021.2.1.2)
- Android Gradle Plugin 7.2.0-alpha02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
an...@google.com <an...@google.com> #18
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Bumblebee Beta 2 (2021.1.1.15)
- Android Gradle Plugin 7.1.0-beta02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
so...@google.com <so...@google.com> #19
The fixes for this issue are now also available in:
- Android Studio Koala Feature Drop | 2024.1.2 Canary 1
- Android Gradle Plugin 8.6.0-alpha01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
an...@google.com <an...@google.com> #20
The fixes for this issue are now also available in:
- Android Studio Iguana | 2023.2.1 RC 1
- Android Gradle Plugin 8.3.0-rc01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
sg...@google.com <sg...@google.com>
cl...@google.com <cl...@google.com> #21
We should try to change the export to machine specification so there's never any conflict instead of adding the merge step of emulated interface descriptor in machine specification. Let's do that before releasing.
Description
With change 85561 the generated machine specification is not longer compatible with previous versions of R8.
Generating
com.android.tools:desugar_jdk_libs_configuration:2.1.0
in96a5fc3f9a34ddc33e4a56861239d813ce9c297b
:With the following diff in the
desugar-jdk-libs
checkout in~/prj/desugar_jdk_libs
:A project using desugared library version 2.1.0 fails Android Studio sync with AGP 8.2.0 with:
Building with
./gradlew :app:assembleRelease
fails the same way:Same for AGP 8.1 and 8.0.