Fixed
Status Update
Comments
al...@google.com <al...@google.com> #2
Hi Ed, Thank you so much for these suggestions. I've been reviewing them and merging them in. Hopefully it should be live. I've included a thank you note too in the article.
ys...@google.com <ys...@google.com> #3
Great! Thanks a lot, I'll look for the live updates soon!
ca...@careem.com <ca...@careem.com> #4
hi all, is there any plan or workaround for this issue? would it be possible to bring back the old signatures that were removed to facilitate the update ? we are starting getting transitive bumps from third parties that are breaking other third parties sdks.
ca...@careem.com <ca...@careem.com> #5
I have a change ready and tested locally where I simply bring back the removed signatures into the class. The change fixes the breaking change coming with constraintlayout-core 1.1.0
.
Should I proceed opening a proposal PR ?
Description
Bumping constraintlayout-core to 1.1.0 from 1.0.4 I got runtime exceptions due to binary incompatibilities between the two versions.
In particular I see incompatibilities with the `androidx.constraintlayout.core.state.Dimension` class.
For example the core version bundled with constraintlayout 2.1.4 (core-1.0.4) had the method `public static Dimension Fixed(int value)` which now is not available anymore (renamed to `public static Dimension createFixed(int value)` ?)
Here is the commit that broke incompatibility for the case above:
Would it be possible to restore compatibility in the new core so we are able to update?