Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[core] Error decode manifest - java.io.IOException: Expected strings start, expected offset #1797

Closed
duckness opened this issue Mar 10, 2023 · 3 comments
Labels
bug Core Issues in jadx-core module

Comments

@duckness
Copy link

Checks before report

Describe error
Unable to open AndroidManifest.xml

Error decode manifest
java.io.IOException: Expected strings start, expected offset: 0x718, actual: 0x714
	at jadx.core.xmlgen.ParserStream.checkPos(ParserStream.java:124)
	at jadx.core.xmlgen.CommonBinaryParser.parseStringPoolNoType(CommonBinaryParser.java:29)
	at jadx.core.xmlgen.BinaryXMLParser.decode(BinaryXMLParser.java:110)
	at jadx.core.xmlgen.BinaryXMLParser.parse(BinaryXMLParser.java:82)

IMPORTANT! attach or provide link to apk file (double check apk version): https://www.apkmonk.com/download-app/com.ibestfin.app.android/7_com.ibestfin.app.android_2022-06-24.apk/

@duckness duckness added bug Core Issues in jadx-core module labels Mar 10, 2023
@duckness
Copy link
Author

FWIW, aapt2 can read the manifest
WindowsTerminal_NQHcjzLLtI

@jpstotz
Copy link
Collaborator

jpstotz commented Mar 10, 2023

The strings section seems to start just 4 bytes later than expected, so fixing was not a big deal.

The fixed version now allows 0 or more bytes offset between string pool header and it's data.

@skylot
Copy link
Owner

skylot commented Mar 10, 2023

Fixed in PR #1798 by @jpstotz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Core Issues in jadx-core module
Projects
None yet
Development

No branches or pull requests

3 participants