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
Possible sharedLibrary issue #936
Issue with current release (2.0.0) and personal snapshot (1fb87e) builds and certain apks on recent LG LP firmware. It seems to be related to related to the recent sharedLibrary implementation.
Steps to reproduce:
This recompiled apk (with no modifications) will produce errors such as the following when the resources are requested:
I've been getting around this so far by removing the sharedLibrary tag from apktool.yml and forcing aapt to the 19.1.0 release, but that is obviously less than ideal. I have verified that the pkg id of the test apk is 0x7f as expected. I would suspect it's adding that tag because it needs lge-res.apk (which is a sharedLibrary)? I haven't looked into it further at this point. Thanks again for this wonderful tool!
What I failed to realize is that this function runs for all apks, frameworks and the apk alike. This means since the real shared framework (
I don't know why you are using a different
That was my understanding from browsing the source as well (that it would only tag sharedLibrary if when it found pkg id 0), but I verified using aapt and just opening resources.arsc in a hex editor that this package has an id of 0x7f, so I figured that it was running against all as well.
I force it to the 19.1.0 aapt because after removing the sharedLibrary tag, building it with the internal (or any 21+ aapt) will fail. Using internal I get a series of errors such as:
W/ResourceType(15641): Entry identifier 0x3 is larger than entry count 0x2
LGLockScreenSettings/res/layout/checkview_layout.xml:4: error: Error: No resource found that matches the given name (at 'id' with value '@id/linearLayout1').
I don't blame you on that. Ever since
No worries at all...and, yeah, I've noticed it has been a bit of a mess. I had a few issues with a project in AS a while back that made me keep the 19.1.0 aapt around so it's no problem for things like this. If there's anything else I can provide/test, feel free to ask. Thanks again for everything.
added a commit
May 5, 2015
As linked above a change has been pushed for the incorrect setting of
I checked out
Apktool latest commit is de3ab0a9e8609f6a631b2c047f352069bb9cfa86
AOSP has had 7 commits to
All these commits look like code cleanup and nothing related to bug fixes.