If the verifier says it can't find the definition of that class, then it literally can't find the definition of that class. So either your build environment is set up wrong, or a jar file has been built wrong. It's not that the verifier can't find a standard java class, it's one of yours (otherwise the verifier would tell you it couldn't find some *different* class).
To be clear com.pachube.jpachube.Data is the class you're missing.. kris On Thu, Dec 8, 2011 at 6:31 PM, Bret Foreman <bret.fore...@gmail.com> wrote: > Kostya, > > That seems possible. The Java code was written without any idea that > it would ever run on Android. But how would I tell from the logcat > what standard Java API it might be using that is unsupported by > Android? So far, I only see the VerifyException for the actual classes > I'm trying to instantiate in my main Android app. > > > On Dec 8, 3:22 pm, Kostya Vasilyev <kmans...@gmail.com> wrote: >> Do those classes in the library, by any chance, reference standard Java >> apis that don't exist in your runtime Android version? >> >> That would cause verification to fail for them, perhaps triggering further >> verification failures up to the activity? > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
