AS 3.6 Canary 12 users heads up: It seems like Co...

# android

[Amirul Zin]

AS 3.6 Canary 12 users heads up:

It seems like ConstraintLayout 2.0.0-beta2 is still broken in AS 3.6 Canary 12, with AGP 3.6.0-alpha12.

It was previously broken on 3.6 Canary 11 with AGP 3.6.0-alpha11 as well.
Some resource linkage is broken when building, e.g.

AAPT: error: resource attr/flow_horizontalSeparator not found
AAPT: error: resource attr/motionProgress not found.

It was previously working fine in AGP 3.6.0-alpha10.

Issue tracked on :
https://issuetracker.google.com/issues/140678030

Possibly related to:
https://issuetracker.google.com/issues/140882056

[wasyl]

Isn’t it similar issue to this one where this comment would help: https://issuetracker.google.com/issues/136103084#comment14?

[Amirul Zin]

Thanks @wasyl for the thread.
Looks like it was fixed as per the last comment but seems like behavior changes in between AGP 3.6.0 alphas are causing this again.
I guess the solution is just to revert back to AGP 3.5.0 for now until the next ConstraintLayout release.

[wasyl]

So adding attributes manually doesn’t help?

[Amirul Zin]

I’m not free to test that solution but they are saying it might overwrite ConstraintLayout attributes on future release.
Not really that ideal if you forget having them somewhere in the first place. In contrast, AGP version is easier to check since it being lock-step-ish with AS canaries 😄