Android和Javamail;更新JDK和ADT后,我收到验证错误?

时间:2012-04-02 15:47:48

标签: android javamail

我以前在我的应用程序中使用过javamail实现,我在这里找到: javamail-android

直到最近,一切正常。我只是在我的构建路径下将.jar文件添加为外部jar。我最近更新到JRE7和ADT 17,现在我正在验证错误!这似乎围绕着javax.mail.Multipart,但我不确定如何解决这个问题。我尝试过的事情:

  1. 将jar添加到lib /,链接源文件夹
  2. 将jar添加到lib /文件夹
  3. 的路径中
  4. 直接添加到构建路径
  5. 添加Multipart.java源文件
  6. 我可以运行应用程序,成功验证凭据,加载IMAP文件夹和消息,但我现在无法获取消息的Multipart内容。这是它似乎失败的地方,偶尔在第一次启动库时。以下是我的追踪:

    W/dalvikvm(16903): VFY: unable to find class referenced in signature (Ljavax/mail/Multipart;)
    I/dalvikvm(16903): Could not find method javax.mail.Multipart.getCount, referenced from method com.control.process.MainActivity.getAttachment
    W/dalvikvm(16903): VFY: unable to resolve virtual method 1033: Ljavax/mail/Multipart;.getCount ()I
    D/dalvikvm(16903): VFY: replacing opcode 0x6e at 0x0002
    D/dalvikvm(16903): Making a copy of Lcom/control/process/MainActivity;.getAttachment code (205 bytes)
    W/dalvikvm(16903): VFY: unable to find class referenced in signature (Ljavax/mail/Multipart;)
    I/dalvikvm(16903): Could not find method javax.mail.Multipart.getCount, referenced from method com.control.process.MainActivity.getMessageBody
    W/dalvikvm(16903): VFY: unable to resolve virtual method 1033: Ljavax/mail/Multipart;.getCount ()I
    D/dalvikvm(16903): VFY: replacing opcode 0x6e at 0x0001
    D/dalvikvm(16903): Making a copy of Lcom/control/process/MainActivity;.getMessageBody code (168 bytes)
    I/ActivityManager(64): Displayed activity com.control.process/.MainActivity: 1229 ms (total 2508 ms)
    W/KeyCharacterMap(16903): No keyboard for id 0
    W/KeyCharacterMap(16903): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
    I/dalvikvm(16903): Could not find method javax.mail.Session.getDefaultInstance, referenced from method com.control.process.MainActivity$ServerCheckTask.doInBackground
    W/dalvikvm(16903): VFY: unable to resolve static method 1038: Ljavax/mail/Session;.getDefaultInstance (Ljava/util/Properties;Ljavax/mail/Authenticator;)Ljavax/mail/Session;
    D/dalvikvm(16903): VFY: replacing opcode 0x71 at 0x0060
    D/dalvikvm(16903): Making a copy of Lcom/control/process/MainActivity$ServerCheckTask;.doInBackground code (2706 bytes)
    W/dalvikvm(16903): VFY: unable to resolve exception class 271 (Ljavax/mail/NoSuchProviderException;)
    W/dalvikvm(16903): VFY: unable to resolve exception class 271 (Ljavax/mail/NoSuchProviderException;)
    W/dalvikvm(16903): VFY: unable to resolve exception class 271 (Ljavax/mail/NoSuchProviderException;)
    W/dalvikvm(16903): VFY: unable to resolve exception class 271 (Ljavax/mail/NoSuchProviderException;)
    W/dalvikvm(16903): VFY: unable to resolve exception class 271 (Ljavax/mail/NoSuchProviderException;)
    W/dalvikvm(16903): VFY: unable to find exception handler at addr 0x1cc
    W/dalvikvm(16903): VFY:  rejected Lcom/control/process/MainActivity$ServerCheckTask;.doInBackground ([Ljava/lang/Object;)Ljava/lang/Object;
    W/dalvikvm(16903): VFY:  rejecting opcode 0x0d at 0x01cc
    W/dalvikvm(16903): VFY:  rejected Lcom/control/process/MainActivity$ServerCheckTask;.doInBackground ([Ljava/lang/Object;)Ljava/lang/Object;
    W/dalvikvm(16903): Verifier rejected class Lcom/control/process/MainActivity$ServerCheckTask;
    D/AndroidRuntime(16903): Shutting down VM
    W/dalvikvm(16903): threadid=3: thread exiting with uncaught exception (group=0x4001b188)
    E/AndroidRuntime(16903): Uncaught handler: thread main exiting due to uncaught exception
    E/AndroidRuntime(16903): java.lang.VerifyError: com.control.process.MainActivity$ServerCheckTask
    E/AndroidRuntime(16903):    at com.control.process.MainActivity.onOptionsItemSelected(MainActivity.java:197)
    E/AndroidRuntime(16903):    at android.app.Activity.onOptionsItemSelected(Activity.java:2282)
    E/AndroidRuntime(16903):    at android.app.Activity.onMenuItemSelected(Activity.java:2170)
    E/AndroidRuntime(16903):    at com.android.internal.policy.impl.PhoneWindow.onMenuItemSelected(PhoneWindow.java:730)
    E/AndroidRuntime(16903):    at com.android.internal.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:139)
    E/AndroidRuntime(16903):    at com.android.internal.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:855)
    E/AndroidRuntime(16903):    at com.android.internal.view.menu.IconMenuView.invokeItem(IconMenuView.java:525)
    E/AndroidRuntime(16903):    at com.android.internal.view.menu.IconMenuItemView.performClick(IconMenuItemView.java:122)
    E/AndroidRuntime(16903):    at android.view.View.onTouchEvent(View.java:4179)
    E/AndroidRuntime(16903):    at android.widget.TextView.onTouchEvent(TextView.java:6541)
    E/AndroidRuntime(16903):    at android.view.View.dispatchTouchEvent(View.java:3709)
    E/AndroidRuntime(16903):    at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:884)
    E/AndroidRuntime(16903):    at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:884)
    E/AndroidRuntime(16903):    at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1643)
    E/AndroidRuntime(16903):    at android.view.ViewRoot.handleMessage(ViewRoot.java:1691)
    E/AndroidRuntime(16903):    at android.os.Handler.dispatchMessage(Handler.java:99)
    E/AndroidRuntime(16903):    at android.os.Looper.loop(Looper.java:123)
    E/AndroidRuntime(16903):    at android.app.ActivityThread.main(ActivityThread.java:4363)
    E/AndroidRuntime(16903):    at java.lang.reflect.Method.invokeNative(Native Method)
    E/AndroidRuntime(16903):    at java.lang.reflect.Method.invoke(Method.java:521)
    E/AndroidRuntime(16903):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
    E/AndroidRuntime(16903):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
    E/AndroidRuntime(16903):    at dalvik.system.NativeStart.main(Native Method)
    

    我唯一的另一个想法是恢复到早期版本的JDK和ADT构建? 需要帮助,任何建议将不胜感激!

    修改

    由于某些原因,在导入必要的jar文件时,mailcap设置被清除。我在阅读Multipart消息之前重新加载了设置,它按预期工作。

    MailcapCommandMap mc =(MailcapCommandMap)CommandMap.getDefaultCommandMap();                         mc.addMailcap(“text / html ;; x-java-content-handler = com.sun.mail.handlers.text_html”);                         mc.addMailcap(“text / xml ;; x-java-content-handler = com.sun.mail.handlers.text_xml”);                         mc.addMailcap(“text / plain ;; x-java-content-handler = com.sun.mail.handlers.text_plain”);                         mc.addMailcap(“multipart / * ;; x-java-content-handler = com.sun.mail.handlers.multipart_mixed”);                         mc.addMailcap(“message / rfc822 ;; x-java-content-handler = com.sun.mail.handlers.message_rfc822”);                         CommandMap.setDefaultCommandMap(MC);

1 个答案:

答案 0 :(得分:0)

由于最近的SDK更改导致了同样的问题:

Dealing with Dependancies

对我来说有用的是从构建路径中删除JARS,重新添加它们并确保它们被标记为已导出。

彼得