Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apktool decode can be tripped up by obfscuators #28

Closed
GoogleCodeExporter opened this issue Mar 18, 2015 · 2 comments
Closed

apktool decode can be tripped up by obfscuators #28

GoogleCodeExporter opened this issue Mar 18, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

Skype for Android uses an obfuscation which trips up apktool when creating
the smali output files:

$ apktool d -d com.skype.android.verizon.apk outI: Baksmaling...
Exception in thread "main" brut.androlib.AndrolibException:
brut.androlib.AndrolibException: File already exists:
out/smali/com/skype/android/verizon/activity/a.java
    at brut.androlib.Androlib.decodeSourcesSmali(Unknown Source)
    at brut.androlib.ApkDecoder.decode(Unknown Source)
    at brut.apktool.Main.cmdDecode(Unknown Source)
    at brut.apktool.Main.main(Unknown Source)
Caused by: brut.androlib.AndrolibException: File already exists:
out/smali/com/skype/android/verizon/activity/a.java
    at brut.androlib.src.SmaliDecoder.decodeClassDefItem(Unknown Source)
    at brut.androlib.src.SmaliDecoder.decode(Unknown Source)
    at brut.androlib.src.SmaliDecoder.decode(Unknown Source)
    ... 4 more


I'm currently using apktool 1.1.1 on Mac OS X. Version 1.0.0 didn't produce
this error but I don't know if the problem existed and was being swallowed
or is actually new.

Please provide any additional information below:
You can get a Skype for Android 1.0.0.6 .apk from
http://www.sendspace.com/file/rnwab1

Original issue reported on code.google.com by sandy...@gmail.com on 30 Apr 2010 at 10:49

@GoogleCodeExporter
Copy link
Author

Actually this is a problem of baksmali, not apktool - I can't fix this. You 
could 
create an issue in smali's issue tracker, but I doubt JF will add some dirty 
hacking 
just to support obfuscated apps on shitty, case-insensitive filesystems. It 
would be 
hard to fix this.

Of course you could use some case-sensitive filesystem and then you shouldn't 
have 
this problem - I'm pretty sure OSX itself is case-sensitive. If you don't want 
to 
convert all your data, you could create some small volume for this purpose.

Original comment by Brut.alll on 31 May 2010 at 1:53

  • Changed state: WontFix

@GoogleCodeExporter
Copy link
Author

Issue 43 has been merged into this issue.

Original comment by Brut.alll on 4 Jun 2010 at 2:23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant