Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

APK Dashboard in Classyshark

DZone's Guide to

APK Dashboard in Classyshark

When browsing an Android app executable file (APK) inside ClassyShark, there is a lot of different information in various APK components, from classes.dex entries to native libraries. Why not have it all in one place?

· Mobile Zone
Free Resource

Download this comprehensive Mobile Testing Reference Guide to help prioritize which mobile devices and OSs to test against, brought to you in partnership with Sauce Labs.

When browsing an Android app executable file (APK) inside ClassyShark, there is a lot of different information in various APK components, from classes.dex entries to native libraries. Why not have it all in one place ?

Since ClassyShark 7.2 the APK view screen is totally re-written and became the APK Dashboard. This screen shows all the important info about your APK and its components. This is the screen we really want you to spend your time on.

You might be wondering how to get to the new APK Dashboard, then ? It is very easy, simply double click the APK name in the tree list on the left-hand side of ClassyShark’s window.

Let’s look at what information you can find there

The Dashboard screen shows both method count and native method count for both classes dex entries and custom loaded classes dex entries

ClassyShark analyses all you classes dex entries for:

  • Duplicate dependencies — having more than one dependency with the same functionality (volley/okhttp, picasso/glide)
  • Server side libraries — libraries that weren’t designed for Android, such as Guava.
  • Deprecated libraries — libraries that are deprecated and not supported anymore, such as Apache HTTP

In addition to those checks ClassyShark analyses your APK’s native libraries:

  • Dynamic Symbol Errors — ClassyShark analyses the APK for the errors on the native libraries side
  • Native Libraries — list of native libraries that the APK has
  • Native Dependencies — native dependencies of the native libraries

You can read this blog post for more details.

Happy coding!

Analysts agree that a mix of emulators/simulators and real devices are necessary to optimize your mobile app testing - learn more in this white paper, brought to you in partnership with Sauce Labs.

Topics:
app ,libraries ,dashboard ,native ,apk ,mobile

Published at DZone with permission of Boris Farber, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}