On Nov 24, 5:20 pm, Kennard Consulting <[email protected]> wrote: > In summary, note that: > > 1. Dalvik is unable to locate > 'org.metawidget.android.widget.AndroidMetawidget' > 2. 'org.metawidget.android.widget.AndroidMetawidget' is in the > original stack trace: it is, in fact, the calling class
You can create a situation like this when exceptions cascade during class loading. Class X causes a load of superclass Y, superclass Y can't be found, the loader for class X sees the failure and throws a new exception. Did the full exception have a "caused by"? One way to track this down with a debugger is: - set a breakpoint on the instruction where things go haywire - when the debugger stops, create an exception breakpoint on Throwable for both caught and uncaught exceptions As soon as anything throws, the debugger will stop. It's also always a good idea to keep an eye on "adb logcat" output in case something weird is going on. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
