search

desword / android-apktool

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

Bad resources.arsc #631

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Download apk from 
https://play.google.com/store/apps/details?id=com.paperlit.android.repubblica
2. Decompile using apktools
3. Recompile without any changes and install apk.
4. Launch app on device: you get an error message (see logcat-error.txt)
5. Unistall app from device.
6. Open recompiled apk with any zip manager
7. Replace resources.arsc from original apk
8. Sign/ZipAlign/Install modified apk 
9. Launch app: no error at all (see logcat-noerror.txt)

What is the expected output? What do you see instead?
Application should start. I get an error message instead.

What version of the product are you using? On what operating system?
apktool_2.0.0rc1.jar on Windows 7 x64

Please provide any additional information below.

Original issue reported on code.google.com by slvrbllt...@gmail.com on 5 May 2014 at 9:15

Attachments:

GoogleCodeExporter commented 9 years ago 
Yes I duplicate, but I think this is application security.

It sends an initial request on sign in, with tons of information from your 
device, including information about the apk. Its possible its failing because 
of recompilation, as none of the decoded smali/res files are changing between 
compiles.

Original comment by connor.tumbleson on 9 May 2014 at 2:09

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Please don't take me wrong but I really don't understand: like I said above, it 
works fine if you take the resources.arsc out of the original apk and put it on 
the recompiled apk. You end up with a definitely recompiled apk, but fully 
working this time.
If nothing changed on the .arsc, then it shouldn't make any difference, but as 
a matter of facts, it does.

Thank you for your support.

Original comment by slvrbllt...@gmail.com on 9 May 2014 at 2:25

GoogleCodeExporter commented 9 years ago 
A quick update. I just realised that using -r option when decompiling gives a 
fully working apk.
So I am afraid that there must be something wrong with the resource handling.

Original comment by slvrbllt...@gmail.com on 10 May 2014 at 7:37