Preverify: VERIFIER ERROR
If you are running Java ME SDK 3.0 Early Access for Mac OS X you might experience preverify problem and got VERIFIER ERROR message. To fix it run following command in /Applications/Java_ME_SDK_3.0.app/Contents/Resources/bin path:
lipo preverify -output preverify -extract i386
It leaves only 32-bit version in the preverify file and takes out the
64-bit version.
It sort of fixed the problem, now I get another preverification error:
Preverifying 309 file(s) into /Users/Iwan/NetBeansProjects/projects/FriendOrFoe/frontend/IFF_FrontEnd/build/JavaME_SDK_3_MSA_Phone1/preverified directory.
Error preverifying class com.sun.lwuit.animations.Transition3D
VERIFIER ERROR com/sun/lwuit/animations/Transition3D.initTransition()V:
Cannot find class javax/microedition/m3g/Node
Is there anywhere defined what is implemented in the EA? Or do I need to use another distribution of LWUIT? One of the sellingpoints of JavaME SDK 3.0 was out-of-the-box support of LWUIT.
Iwan
Posted by Iwan Eising on October 29, 2009 at 09:36 AM CET #
Iwan: LWUIT was not part of EA for Mac. The high-level differences of Mac and Win versions are described at http://java.sun.com/javame/downloads/sdk30.jsp
Posted by Satai on October 29, 2009 at 06:49 PM CET #
Some more details about lwuit in EA
http://forums.sun.com/thread.jspa?threadID=5413745&tstart=0
Posted by kTom on October 30, 2009 at 08:36 AM CET #
Hi,
Could you pl. tell us the solution for the same error on windows.. antenna is failing with javame sdk 3.0 at pre-verification.
Regards,
Raja Nagendra Kumar,
C.T.O
www.tejasoft.com
Posted by Raja Nagendra Kumar on November 12, 2009 at 01:07 PM CET #
We resolved this..
The issue was with latest version of ANTENNA, which was setting the evn path while executing the preverify. When we made this to null, every thing started working as expected.
So far no side effect.. but Antenna team may be able to comment better.
Regards,
Nagendra
Posted by Raja Nagendra Kumar on November 13, 2009 at 03:55 PM CET #
You answered yourself sooner than I did it. This problem should not appear in Windows release. Thank you for your message.
Posted by Radko Najman on November 13, 2009 at 04:07 PM CET #