Fixed
Status Update
No update yet.
Comments
vi...@google.com
di...@gmail.com
SDK tools: 26.1.1
SDK platform-tools: 29.0.1
SDK platform-tools: 29.0.1
tn...@google.com
Fixed by Change-Id: I2b7d1121b553a20fe5b8c5dd883a5475c69dad34 for 3.6 canary 9. Thanks for the report!
di...@gmail.com
Awesome, thanks!
Just curious, were these attributes added as one-off ignores in the detector? Or is there some way to ask AAPT what attributes it backports? Or some other solution? (Not sure how to view the Change-Id)
Just curious, were these attributes added as one-off ignores in the detector? Or is there some way to ask AAPT what attributes it backports? Or some other solution? (Not sure how to view the Change-Id)
tn...@google.com
This is the CL:
https://android.googlesource.com/platform/tools/base/+/06d37c21031d973dc8f6cc768dcf15d0147db26c
It was just added as one-off ignores. There isn't an aapt2 command to query the attributes it backports. I did take a quick look at the source to see what else it was doing; those were the only ones handled in that part of the source code.
It was just added as one-off ignores. There isn't an aapt2 command to query the attributes it backports. I did take a quick look at the source to see what else it was doing; those were the only ones handled in that part of the source code.
Description
Using marginHorizontal, marginVertical, paddingHorizontal, and paddingVertical results in an UnusedAttribute issue being detected. It's technically true that older SDKs didn't have these attributes, but AAPT automatically "desugars" them into corresponding left+right/top+bottom attributes, so the warning can be ignored. I think the issue shouldn't be detected when that AAPT functionality is in place.