search

desword / android-apktool

Automatically exported from code.google.com/p/android-apktool
Other
1 stars 0 forks source link

Invalid icon directories with "aapt dump badging" after repacking (2.0.0-RC3) #726

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Recompile APK file using Apktool v2.0.0-RC3;
2. Launch "aapt dump badging %APK%" on the repacked APK.
For example, official Firefox APK: 
https://ftp.mozilla.org/pub/mozilla.org/mobile/releases/latest/android/multi/fen
nec-34.0.multi.android-arm.apk

What is the expected output? What do you see instead?
Aapt returns invalid directories for APK icons (adding unwanted suffix "-v4"). 
Probably, the reason is Apktool v2.0.0-RC3 which adds 
"platformBuildVersionName" and "platformBuildVersionCode" to 
AndroidManifest.xml.

What version of the product are you using? On what operating system?
Apktool v2.0.0-RC3
Windows 7 64-bit

Original issue reported on code.google.com by kefir...@gmail.com on 12 Dec 2014 at 8:18

GoogleCodeExporter commented 9 years ago 
The bug is unwanted qualifiers (the version one).

The platformVersionName & platformBuildVersionCode are new features in aapt.

Original comment by connor.tumbleson on 14 Dec 2014 at 7:57