Apktool v2.3.2 has been released! This release includes an experimental feature toggle for using the new aapt2 tool, Android Developer P support and a few bug fixes.
As time goes on, more and more applications are built via aapt2. If you try and decode an application built in aapt2, and rebuild it in aapt1 you will more than likely receive some errors. Additionally, rebuilding an application in aapt2 that was originally built with aapt1 will also not work due to the new restrictions aapt2 puts in place.
I've already taken a look at aapt2 at the development level for those interested. This release is intended for the experimental aapt2 support to go out into the wild. A new test suite has begun for aapt2, separate from aapt1, as issues in one might not be experienced in the other.
This release had 57 commits by 1 person.
- Connor Tumbleson (iBotPeaches) - 57 commits
Changes since 2.3.1
- [#1742] - Android P Preview Support
- [#1689] - Initial support for rebuilding with aapt2 binary
- [#1730] - Fixed issue with application with empty
- [#1703] - Fixed issue with root depth kotlin folder not copied
- [#1741] - Fixed building Apktool on Windows
- Added warning if application with non-zero
- Upgraded baksmali to v2.2.2
- Support for treating additional photo extensions (
m4a) as raw
- Prevent temporary BRUT files from clogging temporary directories
If you'd like to take advantage of the experimental aapt2 support, use the parameter
--use-aapt2 when building.
- Apktool 2.3.2
- Rename to
apktool.jarand follow the Instruction Guide if you need help.