Download as PDF, PPTX
Uploaded byBoris Farber
Add ClassyShark to your Android toolbox
This document introduces ClassyShark, a tool for exploring Android application packages (APKs) and Java archives to help diagnose issues like long launch times, crashes, unresponsiveness, and large APK sizes. It discusses common problems ClassyShark can help with, how to open and browse an APK using ClassyShark, and how ClassyShark can be used to diagnose specific issues like obfuscation, dependencies, and architecture support. The document encourages providing feedback on additional features users would find helpful.
Add ClassyShark to your Android toolbox
- 1. Add ClassyShark to yourtoolbox Boris Farber ClassyShark Product Lead Google
- 2. IF YOU HAVEA SMALL APP FORGET THESE SLIDES
- 3. What are themain problems during the app run ?
- 4.
- 5. APK crashes inrelease but not in debug
- 6.
- 7. Large APK (especiallyclasses.dex entries)
- 8. Why my appdoesn’t fit to one classes.dex
- 9. Crashes on certainarchitectures
- 10. What is commonis these problems?
- 11. What is commonis these problems? Hard to identify easy to solve On the APK and not sources level
- 12. What tools dowe have?
- 13. ClassyShark Android and Javaexecutables browser
- 14. If your appis misbehaving in runtime ClassyShark might help you
- 15. To explore yourAPK for class/method signatures To get a lot of useful data about your APK
- 16.
- 17. Let’s take alook
- 18.
- 19.
- 20. Look at methodschart
- 21.
- 22. APK diagnosis withClassyShark
- 23.
- 24.
- 25.
- 26. ClassyShark sees thesame method count as your runtime does!
- 27.
- 28.
- 29. 6. No privatelink
- 30. 7. JNI callsin secondary dexes
- 31. 8. Manifest andresources
- 32.
- 33.
- 34.
- 35.
- 36.
- 37. ● APK ● Dex ●Class ● Jar ● AAR ● Android binary XMLs
- 38. You see whatClassyShark can do ... What would you like ClassyShark to do?
- 39.
- 40.