Open jzbrooks opened 2 months ago
For now, filtering out these images is the best workaround. It's easily done with an exclude
in a gradle file tree if using the plugin, but could be done with the cli tool also.
Seems like the max value is 1 << 15
or 32767
. We should probably break strings along that boundary (at least for VD). Some shorter boundary could make sense considering "long path" lint warnings. Rendering engines probably parallelize drawing individual paths. I haven't seen long paths noticeably impact rendering.
https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/libs/androidfw/StringPool.cpp;l=376;bpv=1;bpt=0 https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/libs/androidfw/StringPool.cpp;l=339;drc=d262a68a1e0c3b640274b094a7f1e3a5b75563e9;bpv=1;bpt=0
Addressing #25 would address this also
It does not break the image, but in the build processes somewhere (AAPT?) the path data string gets replaced with
STRING_TOO_LARGE
. In this case the path data was 159849 chars long.