Open csasd4234234 opened 1 month ago
Have you tried our latest unstable version? It should contain some fixes that might affect this problem.
If the latest unstable version also has problems please provide the APK file that causes this issue. Just rename the APK to ZIP and attach it to this issue.
Or at least upload the AndroidManifest.xml file from within the APK?
I'm sorry I can't provide the app for some reason, but I'm guessing that some special characters in the app are used as the file name to cause the jadx compilation to fail. ![Uploading 2.png…]()
@csasd4234234 Sepecial characters in filename is something I can definitely exclude as cause. The error is about the binary content. But please text the latest unstable version, I am pretty sure that this problem has been already solved.
Issue details
When I use jadx to decompile some apks, I find that the AndroidMainFest.xml cannot be parsed correctly, and when I perform dynamic debugging of the apk, jadx prompts not found app package. But I use GDA and JEB to parse AndroidMainFest.xml files normally.
Relevant log output or stacktrace
Provide sample and class/method full name
Error decode manifest java.io.IOException: Decode error: startNS's attributeSize is not 0x14, position: 0x67fc at jadx.core.xmlgen.CommonBinaryParser.die(CommonBinaryParser.java:39) at jadx.core.xmlgen.BinaryXMLParser.parseElement(BinaryXMLParser.java:269) at jadx.core.xmlgen.BinaryXMLParser.decode(BinaryXMLParser.java:132) at jadx.core.xmlgen.BinaryXMLParser.parse(BinaryXMLParser.java:87)
Jadx version
1.5.0