You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apktool Version (apktool -version) - v2.6.1 (latest)
Operating System (Mac, Linux, Windows) - Windows
APK From? (Playstore, ROM, Other) - Playstore
Stacktrace/Logcat
Below are the logs when running the command apktool d file.apk --only-main-classes , there's already this warning Could not decode attr value, using undecoded value instead: ns=android, name=resource, value=0x7d020000
I: Using Apktool 2.6.1 on com.netflix.mediaclient_8.23.0_build_12_40200.apk
I: Loading resource table...
I: Decoding Shared Library (com.netflix.mediaclient.partnermodule), pkgId: 125
I: Decoding Shared Library (com.netflix.mediaclient.partnermodule), pkgId: 125
W: Skipping package group: com.netflix.mediaclient.partnermodule
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: C:\Users\imenp\AppData\Local\apktool\framework\1.apk
W: Could not decode attr value, using undecoded value instead: ns=android, name=resource, value=0x7d020000
I: Regular manifest package...
I: Decoding file-resources...
I: Decoding values */* XMLs...
I: Baksmaling classes.dex...
I: Baksmaling classes2.dex...
I: Baksmaling classes3.dex...
I: Baksmaling classes4.dex...
I: Baksmaling classes5.dex...
I: Copying assets and libs...
I: Copying unknown files...
I: Copying original files...
I: Copying META-INF/services directory
Steps to Reproduce
apktool d file.apk --only-main-classes
APK
If this APK can be freely shared, please upload/attach a link to it.
The APK can be downloaded from APKMirror using this link
Questions to ask before submission
Have you tried apktool d, apktool b without changing anything? - Yes, apktool fails to rebuild because of the broken xml resources
Are you using the latest apktool version? - Yes
Problem
Right after decompiling the .APK, resources, especially layouts, are missing the namespace in front of each attribute.
For example, instead of having android:layout_width or android:layout_height, there's only layout_width or layout_height, without the appropriate namespace.
Here's an example right after decompilation:
In the example I mentioned, the only defined namespace in that file is android so manually adding android: can fix the issue.
However, in some files there are custom namespaces such as app, in that case it is a bit of a problem to know where and when to replace with android: or app:.
I don't know exactly if this problem is related to the warning mentioned in the logs earlier but right now I am clueless as to why this is happening with this apk file.
The text was updated successfully, but these errors were encountered:
The namespace issue is both a combination of above and some recent changes I reverted/changed for attribute parsing - Correct Attribute Resolution #3123
So I'm going to treat this part of either #2514/#2960 and close it out.
Information
apktool -version
) - v2.6.1 (latest)Stacktrace/Logcat
Below are the logs when running the command
apktool d file.apk --only-main-classes
, there's already this warningCould not decode attr value, using undecoded value instead: ns=android, name=resource, value=0x7d020000
Steps to Reproduce
apktool d file.apk --only-main-classes
APK
If this APK can be freely shared, please upload/attach a link to it.
The APK can be downloaded from APKMirror using this link
Questions to ask before submission
apktool d
,apktool b
without changing anything? - Yes, apktool fails to rebuild because of the broken xml resourcesProblem
Right after decompiling the .APK, resources, especially layouts, are missing the namespace in front of each attribute.
For example, instead of having
android:layout_width
orandroid:layout_height
, there's onlylayout_width
orlayout_height
, without the appropriate namespace.Here's an example right after decompilation:
In the example I mentioned, the only defined namespace in that file is
android
so manually addingandroid:
can fix the issue.However, in some files there are custom namespaces such as
app
, in that case it is a bit of a problem to know where and when to replace withandroid:
orapp:
.I don't know exactly if this problem is related to the warning mentioned in the logs earlier but right now I am clueless as to why this is happening with this apk file.
The text was updated successfully, but these errors were encountered: