jaredrummler / apkparser

APK parser for Android

Entrepreneurial Software Engineer // Founder & CEO at GoatBytes.IO // Android Enthusiast

apkparser's Issues

OutOfMemoryError for when VM heap is too low

If the VM heap is 32MB, and you try to load the app of package name "android" (app label is "Android System") and you run it on the emulator, it gets an OOM:

Caused by: java.lang.OutOfMemoryError
at com.jaredrummler.apkparser.parser.ResourceTableParser.readPackage(ResourceTableParser.java:119)
at com.jaredrummler.apkparser.parser.ResourceTableParser.parse(ResourceTableParser.java:67)
at com.jaredrummler.apkparser.ApkParser.parseResourceTable(ApkParser.java:417)
at com.jaredrummler.apkparser.ApkParser.transBinaryXml(ApkParser.java:269)
at com.jaredrummler.apkparser.ApkParser.parseManifestXml(ApkParser.java:207)
at com.jaredrummler.apkparser.ApkParser.parseApkMeta(ApkParser.java:199)
at com.jaredrummler.apkparser.ApkParser.getApkMeta(ApkParser.java:150)
at com.jaredrummler.apkparser.ApkParser.getAndroidManifest(ApkParser.java:140)

Is there a way to overcome this? To somehow minimize memory usage further?

Questions about the library

1. Can it parse Intent-Filters?
2. How is it in terms of memory? I remember the original library (for PC) was quite memory consuming, which caused OOM sometimes when I tried it on Android:
   hsiafan/apk-parser#19
3. Can you please put a sample too, and not just a library?
   Also, can you split the code , so that it would be possible to use via gradle? Maybe via https://jitpack.io/ ?
4. What about the license? Does it require to put info about the repo in the "about" screen of apps, or something?

Bug: unable to parse some split APK files

Example attached:

split_delight.zip

The crash exception:

    java.lang.Error: com.jaredrummler.apkparser.exception.ParserException: Unexpected chunk Type:203
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1173)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:919)
     Caused by: com.jaredrummler.apkparser.exception.ParserException: Unexpected chunk Type:203
        at com.jaredrummler.apkparser.parser.ResourceTableParser.readChunkHeader(ResourceTableParser.java:204)
        at com.jaredrummler.apkparser.parser.ResourceTableParser.readPackage(ResourceTableParser.java:96)
        at com.jaredrummler.apkparser.parser.ResourceTableParser.parse(ResourceTableParser.java:67)
        at com.jaredrummler.apkparser.ApkParser.parseResourceTable(ApkParser.java:417)
        at com.jaredrummler.apkparser.ApkParser.transBinaryXml(ApkParser.java:269)
        at com.jaredrummler.apkparser.ApkParser.parseManifestXml(ApkParser.java:207)
        at com.jaredrummler.apkparser.ApkParser.getManifestXml(ApkParser.java:126)
        at com.android.apkinstalltest.MainActivity$onCreate$1.run(MainActivity.kt:33)
        at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:289)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 
        at java.lang.Thread.run(Thread.java:919) 

Looking at the manifest xml string that it tried to build, I can see that its result is:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" xmlns:dist="http://schemas.android.com/apk/distribution" android:versionCode="11002120" android:versionName="1.1 (6007940)" android:isFeatureSplit="true" android:compileSdkVersion="29" android:compileSdkVersionCodename="10" package="com.google.pixel.livewallpaper" platformBuildVersionCode="11002120" platformBuildVersionName="1.1 (6007940)" split="delight" split="delight">
	<uses-sdk android:minSdkVersion="28" android:targetSdkVersion="28" />
	<dist:module dist:onDemand="true" dist:title="resourceId:0x7f0d006b">
		<dist:fusing dist:include="false" />
	</http://schemas.android.com/apk/distribution:module>
	<application android:hasCode="false">
		<meta-data android:name="com.android.vending.derived.apk.id" android:value="1" />
	</application>
</manifest>

But according to some online tools, it should have been:

<?xml version="1.0" encoding="utf-8"?>
<manifest android:versionCode="11002120" android:versionName="1.1 (6007940)" android:isFeatureSplit="true" android:compileSdkVersion="29" android:compileSdkVersionCodename="10" package="com.google.pixel.livewallpaper" platformBuildVersionCode="11002120" platformBuildVersionName="1.1 (6007940)" split="delight" split="delight"
  xmlns:android="http://schemas.android.com/apk/res/android"
  xmlns:dist="http://schemas.android.com/apk/distribution">
    <dist:module dist:onDemand="true" dist:title="@2131558507">
        <dist:fusing dist:include="false" />
    </dist:module>
    <application android:hasCode="false">
        <meta-data android:name="com.android.vending.derived.apk.id" android:value="1" />
    </application>
</manifest>

Somehow it got </http://schemas.android.com/apk/distribution:module> instead of </dist:module> .

So this makes it a non valid XML content. Also I noticed other differences, such as "resourceId:0x7f0d006b"

Intent filter is not parsed properly

Try to compare the xml and intent filter of Chrome and youtube. Then intent filter information is not properly captured. Cheers

Request: allow to parse APK file without using File or file-path

Use InputStream , DocumentFile or Uri instead.

The reason:
In the near future, Google will block storage permission, which requires developers to handle files outside of the scope of the current app, to use SAF instead of File and file-path.
More information here:
https://issuetracker.google.com/issues/128591846

And yes, it's very devastating for many apps and libraries that need to access the files in a normal way. Even the Android framework isn't ready for it, as there are functions such as getPackageArchiveInfo (here) that uses a File or file-path, and have no other alternative.

If you want to test your solution without the storage permission and using just the InputStream, here (the app assumes there is a file named "a.apk" on the root path of the normal storage) :
https://issuetracker.google.com/issues/132481545#comment5

Use case of APKParser vs. getPackageManager().getPackageArchiveInfo()

Hi @jaredrummler

I was wondering what the advantages of are of this library in comparison to getPackageManager().getPackageArchiveInfo(). Can you make a small comparison? Currently I am wondering why APKParser exist. What are the drawbacks of getPackageArchiveInfo?

Request: allow to parse only needed things from the APK

For example, if all I want to get from the APK is the intent-filters, if you remove the code of ApkParser.parseResourceTable() , it will save a lot of memory and time for parsing the APKs.

For example, to demonstrate the time difference, I've ran this code on each of the apps that are installed on my device:

                ApkParser apkParser = ApkParser.create(packageInfo.applicationInfo.publicSourceDir);
                try {
                    AndroidManifest androidManifest = apkParser.getAndroidManifest();
                    for (AndroidComponent component : androidManifest.getComponents()) {
                         //nothing
                    }

This took 115,992 seconds to run the code on 241 installed apps (both system and user apps), yet it took 22,864 seconds when removing the code I've written about.

This is about 5 times faster.

It might even be possible to avoid calling other pieces of code, if all I want to get is the intent filters.

How To save a file after editing

Ho to save a file e.g manifest file after changing name or something....

java.lang.RuntimeException: android.os.TransactionTooLargeException

Dex class package name is chinese.

First of all, I really like your work on this APKParser!

But when I try to read all the classes from a dex file,
and they are all chinese, like 慌摮潲摩猯灵潰瑲愯湮瑯瑡潩⽮敋灥;䰯湡牤楯⽤畳灰牯⽴畣瑳浯慴獢䌯獵.

Do you know what is happening?

https://www.bing.com/shop?&entrypoint=edgemmx&PC=EMMX01

@

repo sync

Request: allow to avoid parsing resource table, or at least till it's needed

For a lite usage of this library, only querying basic information about the manifest, you could avoid parsing the resource table, hence improving memory usage and speed of parsing by a huge amount of time.

For comparison, when commenting the "parseResourceTable" function content from ApkParser, I got these results:

Before change: 72,567 ms and up to 86MB of heap memory used for 230 apps, average time: 315ms per app.
After change: 28064 ms and up to 14MB of heap memory usage for the same 230 apps , average time: 122ms per app.

that's x2.5 faster , and x6 more memory friendly.

Question: is it possible to inspect code of APK using this library?

For example like this website:

http://www.javadecompilers.com/

I tried to use the library to get to the dex files, hoping it's the classes, but I got Chinese/Japanese strings:

        thread{
            val appInfo = packageManager.getApplicationInfo("com.whatsapp", 0)
            val apkParser = ApkParser.create(appInfo)
            val dexFiles = apkParser.dexInfos
            for (dexInfo in dexFiles) {
                val dexClasses: Array<DexClass> = dexInfo.classes
                val dexHeader: DexHeader = dexInfo.header
                Log.d("AppLog", "")
            }
        }

DeobfuscationSample.zip

Can I get this project to .jar?

I knew that ApkParser Lib in project is compiled android.

but, I need this library to convert java.(.jar)

Is it possible?

Tech

Why minSdk 14 ?

I think it can be even lower, no?

Bug and possible fix for parsing APK files manifest data

Example is of Chrome and Chrome beta:

chrome and chrome beta.zip

The issue with those seems that it causes attributes to have namespace missing, as such:

<?xml version="1.0" encoding="utf-8"?>
<manifest http://schemas.android.com/apk/res/android:versionCode="398706833" http://schemas.android.com/apk/res/android:versionName="80.0.3987.68" http://schemas.android.com/apk/res/android:compileSdkVersion="29" http://schemas.android.com/apk/res/android:compileSdkVersionCodename="10" package="com.chrome.beta" platformBuildVersionCode="29" platformBuildVersionName="10">
...

Here's the full output of parsing Chrome beta using ApkParser.create(file).manifestXml :

chromeBetaManifestContent.zip

This is considered as invalid XML.

However, I've found a way to parse their manifest anyway. And it seems to fix this issue too .

I made a test, and it seems that I got it right for manifest files of both normal APK files and split APK files. This code is based on this solution on StackOverflow :

ApkManifestFetcher.zip

Please check it out.