Multiple UndefinedResObject errors when decoding APKs from Google Nexus Firmware 4.2.1

[iBotPeaches]

Original issue 425 created by linux.ninj4 on 2013-03-11T11:13:47.000Z:

What steps will reproduce the problem?

1. Get the APKs from Google Nexus Firmware Image 4.2.1 (sorry cannto provide for legal reasons)
2. Call ApkDecoder from java like so:
   ApkDecoder localApkDecoder = new ApkDecoder();

        localApkDecoder.setForceDelete(true);

        localApkDecoder.setOutDir(destination);
        localApkDecoder.setApkFile(apk);

        try {
            localApkDecoder.decode();
            decodeSucseccfull = true;

        }

3.

What is the expected output? What do you see instead?
Expected: apktool continuing extraction without exception
Observed: Multiple AndroLibExceptions for UndefinedResObject (see Attachment):
brut.androlib.err.UndefinedResObject: resource spec: 0x010404d6"
brut.androlib.err.UndefinedResObject: resource spec: 0x01030302"
brut.androlib.err.UndefinedResObject: resource spec: 0x01010457"
brut.androlib.err.UndefinedResObject: resource spec: 0x010404de"

What version of the product are you using? On what operating system?
2d616934a8eaa37c4501868f05c62871 apktool-1.5.2.jar

Please provide any additional information below.

[iBotPeaches]

Comment #1 originally posted by linux.ninj4 on 2013-03-11T11:16:22.000Z:

Sorry, forgot to include list of failing apks

[iBotPeaches]

Comment #2 originally posted by connor.tumbleson on 2013-03-11T11:34:33.000Z:

So this is from a factory image from google? Can you at least tell me what phone so I can go grab the package to test this.

[iBotPeaches]

Comment #3 originally posted by linux.ninj4 on 2013-03-11T14:43:48.000Z:

I will sent you a dropbox link via pm. Thanks for your quick reaction :-)

[iBotPeaches]

Comment #4 originally posted by connor.tumbleson on 2013-03-12T18:49:45.000Z:

Just decompiled all of these without errors. Make sure your framework is up to date (FrameworkFiles).

Just manually delete $HOME/apktool/framework/1.apk and try again. It should work.

[iBotPeaches]

Comment #5 originally posted by linux.ninj4 on 2013-03-17T12:46:19.000Z:

For me the problem persists even after deleteing the framework 1.apk or even the complete apktool folder. Can you provide a hash of your 1.apk?
a20364ad4f723e94bb34d675e89a88a5 apktool/framework/1.apk

[iBotPeaches]

Comment #6 originally posted by connor.tumbleson on 2013-03-17T12:47:47.000Z:

md5ibotpeaches@raganok:~/apktool/framework$ md5sum 1.apk
a20364ad4f723e94bb34d675e89a88a5 1.apk

They match. Still I don't receive this problem.

[iBotPeaches]

Comment #7 originally posted by linux.ninj4 on 2013-03-17T13:04:06.000Z:

Weird. How can we skip resource dedcoding

[iBotPeaches]

Comment #8 originally posted by connor.tumbleson on 2013-03-17T13:08:06.000Z:

 -r, --no-res
        Do not decode resources.

[iBotPeaches]

Comment #9 originally posted by linux.ninj4 on 2013-03-17T13:18:33.000Z:

Yeah that is from the commandline. We're directly using ApkDecoder via the jar. I tried to use ApkDecoder.setDecodeResources but my eclipse keeps complaining that it cannot find the necessary constant. Just a wild guess, but maybe there is another (older) version of androlib in my classpath.

[iBotPeaches]

Comment #10 originally posted by linux.ninj4 on 2013-03-17T13:27:12.000Z:

Rechecked. None of my dependencies ships with another version of androlib.

[iBotPeaches]

Comment #11 originally posted by connor.tumbleson on 2013-03-17T13:31:46.000Z:

O. Yeah, I don't think ApkDecoder is abstracted enough for use like that. I'll have to make a note to support its use independently.