Fixed
Status Update
Comments
xa...@google.com <xa...@google.com> #2
I'm also seeing this issue with Material Components 1.3.0 and ConstraintLayout 2.1.0-alpha2
xa...@google.com <xa...@google.com> #3
Fixed with 2.1.0-beta01
xa...@google.com <xa...@google.com> #4
We are going to revert the change and release a new build.
td...@google.com <td...@google.com> #5
If it's helpful I have more detail and an internal repro in b/109893035 using the feature plugin. Feel free to reach out if you need more information.
or...@gmail.com <or...@gmail.com> #6
"We are going to revert the change and release a new build" Any estimates at this point regarding when this might happen? Thanks, John
xa...@google.com <xa...@google.com> #7
As soon as we can but probably a few days at least unfortunately.
xa...@google.com <xa...@google.com> #8
This should be fixed in Canary 18 which is now out.
or...@gmail.com <or...@gmail.com> #9
Just tried it here and confirmed it fixed the issue.
ce...@gmail.com <ce...@gmail.com> #10
It works for me :-)
lo...@gmail.com <lo...@gmail.com> #11
I had the same issue that I reported and was marked as a duplicate, and what fixed it what updating the Android Gradle Plugin from 3.2.0-alpha17 to 3.2.0-alpha18. It seems the Android Gradle Plugin being out of sync with the IDE caused the issue, but the IDE complained about the kotlin-android gradle plugin instead
Description
Probably related to go/ag/I97a15ea8f0121f665bb740d3d5e68e6608ccce51 ?
We do have Kotlin tests so I'm not sure why this would fail for these devs.
Chris, can you investigate?