VFY: unable to find class referenced in signature

by hefeng » Tue, 07 Jul 2009 00:06:43 GMT


Sponsored Links
 Hello,

I try to port the XMPP library to android sdk 1.5, follow the demo
ApiDemo from the sdk,  I created a directory something like below:

      smack--+AndroidManifest.xml                          ..The
manifest for the smack library

                    |
 
+src                                                     ..The source
code for the smack
                    :
                    :
                    ------
test                                              .. The test
directory for the test case
                                  |
                                 +
AndroidManifest.xml                              .. The manifest for
the test code
                                  |
                                  :
                                  :
 
+src                                                            .. The
test code for the smack library.

After I build both projects, I install them respectively on the
emulator, then I launch the test case by command:
$ adb shell am instrument -w org.jivesoftware.smack.test/
android.test.InstrumentationTestRunner

then console output following information:
$INSTRUMENTATION_RESULT: shortMsg=org.jivesoftware.smack.LoginTest
$INSTRUMENTATION_RESULT: longMsg=java.lang.VerifyError:
org.jivesoftware.smack.LoginTest
$INSTRUMENTATION_CODE: 0

I think there is something wrong with the test case then I check with
command:

$adb logcat

I found following error message in the log:
:
:
D/AndroidRuntime( 1216): --- registering native functions ---
D/ActivityManager(  564): Uninstalling process
org.jivesoftware.smack.test
I/ActivityManager(  564): Start proc org.jivesoftware.smack.test for
added application org.jivesoftware.smack.test: pid=1223 uid=10019 gids=
{}
W/dalvikvm( 1223): VFY: unable to find class referenced in signature
(Lorg/jivesoftware/smack/XMPPConnection;)
E/dalvikvm( 1223): Could not find method
org.jivesoftware.smack.XMPPConnection.connect, referenced from method
org.jivesoftware.smack.LoginTest.testInvalidLogin
W/dalvikvm( 1223): VFY: unable to resolve virtual method 176: Lorg/
jivesoftware/smack/XMPPConnection;.connect ()V
:
It seems there is something wrong for the dalvik to resolve the
connect method in the org.jivesoftware.smack package, so I type the
command

$ adb shell dexdump -d -f -h /data/dalvik-cache/
d...@app@org.jivesoftware.smack....@classes.dex | grep XMPPConnection

then, I find following information in output
    #4              : (in Lorg/jivesoftware/smack/XMPPConnection;)
013130:                                        |[013130]
org.jivesoftware.smack.XMPPConnection.connect:()V

It seems that the XMPPConnection class with its method have been
install properly already.



--~--~---------~--~----~------------~-------~--~----~



VFY: unable to find class referenced in signature

by hefeng » Tue, 07 Jul 2009 00:07:21 GMT


 Hello,

I try to port the XMPP library to android sdk 1.5, follow the demo
ApiDemo from the sdk,  I created a directory structure something like
below for two packages org.jivesoftware.smack &
org.jivesoftware.smack.test :

      smack--+AndroidManifest.xml               ..The manifest for
package org.jivesoftware.smack

                    |
 
+src                                                 ..The source code
for the smack
                    :
                    :
                    ------
test                                          .. The test directory
for the test case
                                  |
                                 + AndroidManifest.xml              ..
The manifest for the package   org.jivesoftware.smack.test
                                  |
                                  :
                                  :
 
+src                                                            .. The
test code for the smack library.

After I build both projects, I install both package respectively on
the emulator, then I try to launch the test case by command:
$ adb shell am instrument -w org.jivesoftware.smack.test/
android.test.InstrumentationTestRunner

then console output following information:
$INSTRUMENTATION_RESULT: shortMsg=org.jivesoftware.smack.LoginTest
$INSTRUMENTATION_RESULT: longMsg=java.lang.VerifyError:
org.jivesoftware.smack.LoginTest
$INSTRUMENTATION_CODE: 0

I think there is something wrong with the test case then I check with
command:

$adb logcat

I found following error message in the log:
:
:
D/AndroidRuntime( 1216): --- registering native functions ---
D/ActivityManager(  564): Uninstalling process
org.jivesoftware.smack.test
I/ActivityManager(  564): Start proc org.jivesoftware.smack.test for
added application org.jivesoftware.smack.test: pid=1223 uid=10019 gids=
{}
W/dalvikvm( 1223): VFY: unable to find class referenced in signature
(Lorg/jivesoftware/smack/XMPPConnection;)
E/dalvikvm( 1223): Could not find method
org.jivesoftware.smack.XMPPConnection.connect, referenced from method
org.jivesoftware.smack.LoginTest.testInvalidLogin
W/dalvikvm( 1223): VFY: unable to resolve virtual method 176: Lorg/
jivesoftware/smack/XMPPConnection;.connect ()V
:
It seems there is something wrong for the dalvik to resolve the
connect method in the org.jivesoftware.smack package, so I type the
command

$ adb shell dexdump -d -f -h /data/dalvik-cache/
d...@app@org.jivesoftware.smack....@classes.dex | grep XMPPConnection

then, I find following information in output
    #4              : (in Lorg/jivesoftware/smack/XMPPConnection;)
013130:                                        |[013130]
org.jivesoftware.smack.XMPPConnection.connect:()V

It seems that the XMPPConnection class with its method have been
install properly already, then I lost ideal how to finger out the
problem, please give me a hand, any comments are appreciated.

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


VFY: unable to find class referenced in signature

by fadden » Tue, 07 Jul 2009 03:41:15 GMT


 


I'd guess that the org.jivesoftware.smack.apk file is not present in
the process responding to the instrumentation test request.

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Events not catched on real device using Activity.dispatch<EventType>

Hello all!

I am creating a game in which the user can control a ship by
- Using DPAD
- Using touchscreen
- Using trackball
- And even using orientation events (roll pitch etc)


It all works on the emulator but when i open the game on a real device
then
the events (touch, trackball) do not work anymore.

I am catching evetns by overriding the dispatch<EventType>() methods.
This is the code in my Activity class that catches the events:


  public boolean dispatchKeyEvent(KeyEvent e) {
                super.dispatchKeyEvent(e);
                return controller.onKeyEvent(e.getKeyCode(), e);
        }

        public boolean dispatchTrackballEvent(MotionEvent e) {
                if(settings[2] || settings[3]) {
                        return controller.onTrackballEvent(e);
                } else {
                        return super.dispatchTrackballEvent(e);
                }
        }

        public boolean dispatchTouchEvent(MotionEvent e) {
                if(settings[1]) {
                        return controller.onTouchEvent(e);
                } else {
                        return super.dispatchTouchEvent(e);
                }
        }

I think the dispatchKeyEvent(..) method works fine, but the other ones
do not work on a real device.
They work without problems on the emulator.

What am i doing wrong?
I really do not understand it.

Thanks in advance.

-
Tjerk Wolterink


--~--~---------~--~----~------------~-------~--~----~

2. How do you modify the call log

Can anyone tell me how to modify the call log?  What permissions do i
need and is it possible to get some basic code to show how?  just a
few lines not whole classes or anything.

thanks

Chris
--~--~---------~--~----~------------~-------~--~----~

3. how to use touch-lens as keypad

4. draw text as big as possible inside a rectangle

5. adb version

6. Eclipse warning

7. Am I leaking bitmaps from adapter's getView ?