dexSplitter
Introduction: Analyze contribution rate of each module to the apk size
Tags:
As we all know, Google has provided aapt plugin for parsing apk, we can get a list of apk files by using 'aapt l -v '. We can divide each res file(assets file) into the module project which it belongs to. But source code of the project can not be divided directly because it will be shrinked optimized and obfuscated. DexSplitter can help you to divide source code.
Scenarios
- Analyze contribution rate of each module to the apk size
Diff the size of each module in the apk for every sprint
Apk Split Result
Android Origin Build Release.apk
DexSplitter Build Release.apk
splitter_result.txt
ps:more details:extra/hack_description.txt extra/hook_details.txt
Demo Introduction
The most important purpose of dexSplitter is to build apk which has special dex filesYou can use extra/dx.jar directlyHost app(lib:gson), library module moduleone(lib:GreenDAO), library module moduletwo(lib:universalimageloader)subdexeslist.txt is used for splitting dex, TestClassForMainDex.class is just a test fileThird libs will not be obfuscatedAndroid Support library is marked as android_syssubdexeslist.txt should not contain duplicated class files
Schematic Diagram

Implementation
Divide the dex files with class files- Build apk which has special dex files
Python files for collecting class filesObfuscated class list for release version
Future
Signed apkGenerate tables about the proportion of module projectsParse changes of dex files by comparing different apk versionsDivide the dex files by author, module etc.
License
- Copyright (c) 2018-present, iQIYI, Inc. All rights reserved. Most source code in dexSplitter are MIT licensed. Some other source code have Apache licenses. Please refer to the LICENSE file for detailed information.



