Connor Tumbleson
Connor Tumbleson
Taking this AndroidL / API32 a bit differently than other upgrades. We have many things to do * Support the new ASRC changes (roughly done) * Adopt those ASRC changes...
I've merged updates to aapt2/aapt for these new properties. Still have: * Adopt those ASRC changes into viable format to re-use/re-parse during compilation Remaining
That does appear to be an issue.
well actually, this may be right. Just too much verbose output. What if those resources are actually staged aliases because of API 32 not yet finalized?
Okay, if thats the only thing remaining. I believe thats covered in #2514 (for the multi-package support)
I appreciate the research you did as I read my email on this ticket @MartinDupont
We tried this [once](https://github.com/iBotPeaches/Apktool/pull/2463) and I was hesitant, maybe for 3.0. Marking as feature.
Confirmed. Marking as bug.
@pashamcr I'm not following how `unescaping` XML in a function that is called `escaping` has anything to do with a proper fix here. Can you give some background on to...
thank @pashamcr for the detailed breakdown. It looks like the issue is somewhere prior where we are improperly encoding resources (or just picking a few) while we could probably just...