Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Apk built with dexguard is not getting decoded. #1014
I am working on project where I need to decode apks built by our dev team as part of build processing.
Eventhough errors are diff, I suspect underlying problem is same, apktool is not able to read resource table.
output of team apk:
output of test apk:
changed the title from
Apk built with dexguard is getting decoded.
Apk built with dexguard is not getting decoded.
Aug 3, 2015
referenced this issue
Aug 4, 2015
and holy cow this is an improvement over previous versions of Dexguard.
This enterprise version obfuscates/encrypts resources. I'm not sure how it does this, unless it decrypts them on the fly, but apktool's responsibility is simply decoding the apk. I will see what I can do.
Made progress on this after committing - eabb7d8
This is another creative tweak. All resources have different IDs, but their names aren't visible to me, so they are set to
A update for this. As my last update said, there are resources which names decode to an empty value. Which might be a decode failure of some crazy UTF8 char, or literally an empty value.
So there are 2 problems that arise here.
I patched these, but this introduces an APK that is obviously not like the original, but hey the decode works. That counts for something right?
So then I started looking at the dummy resources. The values of the resources are legit and used sometime, but the name of such resource is bogus and thus replaced with
So can we build the apk back? Not all, we then run into the #885 bug (Which means a custom
Merry Christmas, btw.
Since the last thing in this bug is actually Bug #885, I'm closing this to help clean up the tracker. My guess is that once Android N drops and aapt2, I'll have to rediscover all my patches to the binary and at that point I can patch it to allow non-standard characters.