Closed GoogleCodeExporter closed 9 years ago
Its actually a style problem. Whether its
1) The style isn't in the frameworks included
2) Invalid resources on decode which are those resources
3) A bug
I'm inclined its either 1 or 2, like the other times this bug has come up. It
would help to have the APK though. You may email it to me or attach it.
Original comment by connor.tumbleson
on 24 Jul 2014 at 6:48
Thank you so much for the prompt reply, unfortunately I cannot email/attach the
apk file due to Non-disclosure agreement.
Can you possibly let me know that how can I add the particular style to the
framework?
when you mean by framework, are you talking about the APK tool framework(i.e
1.apk)?
Can you also elaborate on "Invalid resources on decode which are those
resources"?
Original comment by vju...@gmail.com
on 24 Jul 2014 at 6:58
1) Adding styles is as easy as finding the styles.xml from AOSP / other roms
and adding them to the local res/values/styles.xml (in order to add missing
styles)
2) Yes, the resources apktool makes in $HOME/apktool/frameworks/
3) Run "aapt d resources name_of_apk.apk > file" Grep file for "INVALID". If
you find something like this
"INVALID TYPE CONFIG FOR RESOURCE 0x7f0200ba" then aapt or apktool couldn't
identify the configuration of the resource. So apktool replaces it with a dummy
value of false. If this happens to be a style, then you no longer have it. I
don't know a way around this problem, except finding the styles via 1) and
adding them in.
Original comment by connor.tumbleson
on 24 Jul 2014 at 7:07
when I enter the command you mentioned I get the following list:
.Widget.Base.ActionBar.Menu: <bag>
resource 0x7f0b0053 com.app_one.ida.android:style/TextAppearance.AppCompat
.Widget.Base.ActionBar.Title: <bag>
resource 0x7f0b0054 com.app_one.ida.android:style/TextAppearance.AppCompat
...
...and so on
so does that mean I don't have the style?
Original comment by vju...@gmail.com
on 24 Jul 2014 at 7:26
Thats the expected list, there is no problem with those two resources. Are
there any lines that are "INVALID TYPE CONFIG FOR RESOURCE" in there?
Original comment by connor.tumbleson
on 24 Jul 2014 at 7:27
I checked thoroughly, there are such line that say "INVALID TYPE CONFIG FOR
RESOURCE" .
Original comment by vju...@gmail.com
on 24 Jul 2014 at 7:31
My apologies, I meant there No such lines.
Original comment by vju...@gmail.com
on 24 Jul 2014 at 7:32
Finally it worked, I used the beta version of the Apt tool, just made changes
in the apktool batch file :
@echo off
set PATH=%CD%;%PATH%;
java -jar "%~dp0\apktool_2.0.0b9.jar" %1 %2 %3 %4 %5 %6 %7 %8 %9
And I was able to recompile with no errors.
Original comment by vju...@gmail.com
on 25 Jul 2014 at 2:14
Issue 663 has been merged into this issue.
Original comment by connor.tumbleson
on 4 Aug 2014 at 11:53
[deleted comment]
Issue 665 has been merged into this issue.
Original comment by connor.tumbleson
on 7 Aug 2014 at 12:06
Issue 669 has been merged into this issue.
Original comment by connor.tumbleson
on 16 Aug 2014 at 3:11
Issue 678 has been merged into this issue.
Original comment by connor.tumbleson
on 24 Sep 2014 at 12:20
Same issue with com.greenbeansoft.CheckmarkLite application.
Apktool v2.0.0-RC3 - a tool for reengineering Android apk files
with smali v2.0.3 and baksmali v2.0.3
AAPT extracted from apktool
Had to add 11 style definitions for APK to compile
Original comment by fr0st.br...@gmail.com
on 8 Dec 2014 at 4:10
I will add a Wiki entry explaining the process of adding themes internally to
an APK, since app developers utilized private resources :(
Since I don't believe its Apktool's job to identify missing themes and find
them / install them. I will close this.
Original comment by connor.tumbleson
on 26 Dec 2014 at 12:36
Original issue reported on code.google.com by
vju...@gmail.com
on 24 Jul 2014 at 6:30