src/test/java/net/dongliu/apk/parser/ApkFileTest.java | 51 0 + 51 - 0 !
src/test/java/net/dongliu/apk/parser/ByteArrayApkFileTest.java | 46 0 + 46 - 0 !
2 files changed, 97 deletions(-)

 remove file test since our source does not have apk file

src/main/java/net/dongliu/apk/parser/bean/ApkMeta.java | 12 12 + 0 - 0 !
src/main/java/net/dongliu/apk/parser/parser/ApkMetaTranslator.java | 2 2 + 0 - 0 !
2 files changed, 14 insertions(+)

 parse the debuggable information

Apps can be build in debug or in release mode. `./gradlew assembleDebug`
vs `./gradlew assembleRelease`. If the app is debuggable the Android OS
allows to attach the debugger and other development features. In release
mode these are restricted.

The AndroidManifest flag is documented here:

    https://developer.android.com/guide/topics/manifest/application-element#debug

Since this information is quite handy, add it to the parser.

(cherry picked from commit a37ae21deedac50e7469139e0adfd6ba153333b4)

src/main/java/net/dongliu/apk/parser/parser/ResourceTableParser.java | 12 7 + 5 - 0 !
1 file changed, 7 insertions(+), 5 deletions(-)

 don't crash with a buffer underflow when packagecount == 0

(cherry picked from commit 01ef8bf9ff74e224af0935b4e8f7aebad415d7f3)

README.md | 57 29 + 28 - 0 !
1 file changed, 29 insertions(+), 28 deletions(-)

 readme reworked

(cherry picked from commit 59714765745c77afba78b9ceee558ea11fd5869a)