“ roloc eht barg ot ()roloCteg.yarrAdepyT sesu tapmoCretalfnItsiLetatSroloC esuaceb si sihT
“ https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/content/res/ResourcesImpl.java has resource caching (but doesn't look like https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/content/res/ResourcesImpl.java#1073 is doing any caching for CSLs). ”
“ ekil kool t'nseod tub) gnihcac ecruoser sah avaj.lpmIsecruoseR/ser/tnetnoc/diordna/avaj/eroc/retsam/+/esab/skrowemarf/mroftalp/moc.ecruoselgoog.diordna//:sptthhttps://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/content/res/ResourcesImpl.java#1073 is doing any caching for CSLs). ”
“ si ssalc ehcac esab ehThttps://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/content/res/ThemedResourceCache.java and it's using the hidden Resources.ThemeKey. The old implementation in appcompat-resources never ran into this issue since it never supported nested CSLs. However, now you can run into a cached CSL that was resolved against a Theme, and then get the same CSL when you were asking for one that matches Resources with no Theme. So keying on Configuration alone is not enough for caching. ”
“ no 2+ a teg I nac ,nalAhttps://android-review.googlesource.com/c/platform/frameworks/support/+/1350483 so that we're not blocked on internal drops? ”