Android Studio introduces another quite useful tool that allows you to see what the resulting apk has produced - the Apk Analyzer. Create an , insert the following code, and run the project: ApkAnalyzerActivity class ApkAnalyserActivity : AppCompatActivity() {
   override fun onCreate(savedInstanceState: Bundle?) {
       super.onCreate(savedInstanceState)
   }
} Run the and select the current : Apk Analyzer app-debug.apk If b didn't find it on its own, find it yourself at the following address: A window with a list of files will open: In it, you can find the familiar folders and files: res, assets, , as well as classes.dex files and folders with libraries, such as . For this article, I specially inserted into a large project, so that you can see the difference. AndroidManifest.xml okhttp3 ApkAnalizerActivity Go to the file, insert and restart the project: build.gradle multiDexEnabled false Note that there are fewer files. In one of these files, at the package address of the current , you can find it. classes.dex ApkAnalyzerActivity Right-click it and choose : Show Bytecode You can view the of the current here: bytecode ApkAnalyzerActivity Select from the list and view the contents of this file: AndroidManifest.xml Note that is not only a version of the current application but a mortal version of the current application and all the modules and libraries that are part of it. AndroidManifest.xml Go back to the file, enable obfuscation (change the line), restart the project and open : build.gradle minifyEnabled true Apk Analyzer Click on any file: classes.dex Note that all files and methods have changed their names because of obfuscation and are now a random set of characters. Also, note the rightmost column with the file sizes: You can use this column to monitor file size and keep track of anomalies, such as when a file is too heavy. Conclusion The is quite a powerful tool that should not be ignored during development. It is especially useful in cases where: Apk Analyzer Observing the result of obfuscation. Examination of the resulting . AndroidManifest.xml Detection of abnormal file sizes. Studying the compiled resources.

Super

Autofill Fields with Adb and External Tools

Using Markdown Math in Github

Nominated for 2022 - Android Advocate of the Year

Too Long; Didn't Read

Make resilience your competitive advantage

How to Use APK Analyzer in Android Studio

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

6 Ways to Run Kotlin Code in Android Studio

Java bits: 0xFF and 0xFFL

10 Things You Didn't Know You Could Do With Google Keep

10 Things to check on Android code reviews

10 Mistakes In Mobile App Development That Make You Look Dumb

6 Ways to Run Kotlin Code in Android Studio

Java bits: 0xFF and 0xFFL

10 Things You Didn't Know You Could Do With Google Keep

10 Things to check on Android code reviews

10 Mistakes In Mobile App Development That Make You Look Dumb

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps