I'm debugging a closed-source Android app with jdb. In the output produced by the apktool, I see class com.myapp.j.d.d, as well as a/b/c/e, but at run-time, I see only com.myapp.j.d.e. Why is that happening?

1 Answer 1


One possibility is that the classes fail verification. If this is the case, when you install the apk, you'll see messages from art in logcat with details about which class failed verification and why.

  • logcat reports nothing about this app. It must be something else!
    – assp1r1n3
    Sep 3, 2016 at 19:56
  • 1
    Most class verification happens when the apk is installed. Are you sure you're looking at logcat while the apk is being installed, rather than when running the app?
    – JesusFreke
    Sep 3, 2016 at 22:42
  • Oh, I forgot that in 4.4+ ART is AOT. Reinstalled the app, but logcat is still silent
    – assp1r1n3
    Sep 3, 2016 at 22:49
  • Well, that was the case even in dalvik :). If there's no verification error, then I don't know why the class wouldn't be present.
    – JesusFreke
    Sep 4, 2016 at 1:08
  • Dynamic loading and unloading of the class during the execution?
    – assp1r1n3
    Sep 4, 2016 at 1:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.