Fixed
Status Update
No update yet.
Comments
yb...@google.com
Is this fixed? I'm still seeing this issue with AGP 8.1.0-beta01 + Gradle 8.1
yb...@google.com
The fix has not been landed.
za...@gmail.com
Due to this bug in CI we hit configuration cache invalidation 100% of the time. Can we make sure the fix lands soon? And especially before 8.1.0 stable.
za...@gmail.com
I cc'ed you on the CL which should be landed this week.
yb...@google.com
da...@google.com
Aurimas, is this 8.1 blocking for Androidx? If not, feel free to remove the "Blocking release" label.
Description
Version used: 1.1.0-present
Theme used: NA
Devices/Android versions reproduced on: NA build-time
- Relevant code to trigger the issue: Any kotlin data class in an external module. Building the following project can reproduce it:
In Kotlin, data classes will have a primary constructor and sometimes generated synthetic constructors. ROOM's processor will complain about the presence of the synthetic ones (which are usually visible when reading the class file from an external library), but since it's reading metadata it could use it to find the "primary" constructor to know for sure.
Example:
The solution would be to find that constructor, then match it to the corresponding constructor as seen in the elements API