Closed Arczi008TV closed 5 years ago
Could have sworn we have a patch already for qmg
, guess we had some regression.
This helped find an interesting bug in our copying of raw assets. If the directory path of incoming/outgoing is different, we screw up the copying - leading to these errors.
Basically the implicit addition of version qualifiers was breaking this. Should have a patch up today.
➜ Bug2064 apktool d Deodexed_SecLauncher2.apk -t 2064 -f
I: Using Apktool 2.4.1-cc194d-SNAPSHOT on Deodexed_SecLauncher2.apk
I: Loading resource table...
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: /Users/connortumbleson/Library/apktool/framework/1-2064.apk
I: Regular manifest package...
I: Decoding file-resources...
I: Decoding values */* XMLs...
I: Baksmaling classes.dex...
I: Copying assets and libs...
I: Copying unknown files...
I: Copying original files...
➜ Bug2064 apktool b Deodexed_SecLauncher2
I: Using Apktool 2.4.1-cc194d-SNAPSHOT
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Checking whether resources has changed...
I: Building resources...
I: Building apk file...
I: Copying unknown files/dir...
I: Built apk...
➜ Bug2064
Patch above
Information
apktool -version
) - apktool 2.4.0Stacktrace/Logcat
Steps to Reproduce
apktool d SecLauncher2.apk
Frameworks
https://www43.zippyshare.com/v/YoPrh2oc/file.html
APK
https://www114.zippyshare.com/v/O1dDSybh/file.html (odexed version, only apk here) https://www34.zippyshare.com/v/0pkkrcLx/file.html (same but deodexed apk)
Questions to ask before submission
apktool d
,apktool b
without changing anything? - YES, apk crashingAre you using the latest apktool version? - YES