Join GitHub today
Add option to force decoding of AndroidManifest.xml #1680
Forces decoding of AndroidManifest.xml, even if
I have set it to be an advanced option, named
If accepted, I can submit another pull request regarding
Thanks again! Worked great and added a few tests to prevent regressions.
The docs repo needs a slight update for new parameters, but the local spin up of docs (or mine) is having some troubles. So no worries on updating docs. I'll get those added when I get docs working locally again.
added a commit
this pull request
Dec 7, 2017
Is it possible to recompile if we set both flags --force-manifest and --no-res ? I tried it but it doesn't work. The manifest file will be considered as corrupted and the package won't install.
The thing is that I need to perform some changes to the manifest file without decompiling the resources (which is problematic most of the times), then rebuild the package.
It seems that the build feature does not recompile the manifest file when --no-res flag was used during unpack. The manifest file will be in ascii form after recompile.
Any solution? Thanks.