06-11-2009 09:18 AM
I have an app that runs fine on simulator, but not on devices.
I am building it with the 188.8.131.52 JDE for the Storm and running on a Storm with os 184.108.40.206. The app is signed for RRT, RBB and RCR.
Can someone please help me identify what things may cause this problem?
Extract from eventlog
guid:0x97C9F5F641D25E5F time: Thu Jun 11 11:22:03 2009 severity:0 type:2 appystem data:CMM: Fireworks(1085) no sig from 0x33
guid:0x97C9F5F641D25E5F time: Thu Jun 11 11:22:03 2009 severity:0 type:2 appystem data:VM:LINK Fireworks
guid:0x97C9F5F641D25E5F time: Thu Jun 11 11:22:03 2009 severity:0 type:2 appystem data:
guid:0x97C9F5F641D25E5F time: Thu Jun 11 11:22:03 2009 severity:0 type:2 appystem data:Linker error: 'VerifyError' for Fireworks
guid:0x97C9F5F641D25E5F time: Thu Jun 11 11:22:03 2009 severity:0 type:2 appystem data:Error starting Fireworks: Error loading module 'Fireworks' VerifyError.
guid:0x9C3CD62E3320B498 time: Thu Jun 11 11:22:03 2009 severity:1 type:3 app:Java Exception data:
Error starting Fireworks: Error loading module 'Fireworks' VerifyError.
06-11-2009 09:33 AM
In JDE/bin folder there is preverify.exe utility.
Use it with *.jar (not cod) file of your project and specify location of the relevant net_rim_api.jar library.
preverify.exe -classpath c:\jde4.7\lib\net_rim_api.jar c:\myapps\myapp.jar
06-11-2009 09:56 AM
I'm afraid I dont see how to interpret the results. preverify doesn't display any messages and in the output folder it created it just put a copy of the fireworksjdeproject.jar
06-11-2009 10:06 AM - edited 06-11-2009 10:06 AM
If preverify does not blame on this file, then it is ok from it's point of view.
So, let's find out the code that causes the problem.
Copy all your project files to different folder with name, let say DebugProject
Now, exclude parts of your code from your application and check it on actual device.
As verification error disappears then inspect very closely the code part you have removed last.
06-11-2009 11:27 AM
It seems that if I disable to use of extends Persistable my app starts to work.
But this is still confusing me as the system we have used in several products hasn't changed recently.
We have an interface "public interface CAWSerializable extends Persistable" which we implement on any object we want to persist. And our persistent object handler takes the object and adds it to CAWBasePersistentHashtable which extends form Hashtable.
I suppose it must be down to one of the objects I am putting into store. I will keep pulling things out until I can find some more information to post.
06-11-2009 12:28 PM
Make sure you are using the following import directive for Persistable interface:
In case you are using another import directive, for example: import net.rim.device.api.vm.Persistable; it may be cause of the problem.
06-11-2009 05:38 PM
Interesting, I didn't know about the vm.Persistable import.
Just did a quick check and yes I have
So I'll keep investigating tomorrow. Thanks for the information.
06-17-2010 01:37 AM
I am a BlackBerry site owner/editor in chief and I am getting this error after I try to start a third party app that I've just downloaded. It only happens on apps not themes. Never happens when I update an app to a new version. For instance I chose to download LED by The Jared Company and Gowalla both The error reads: "Error starting Gowalla: Error loading module 'Gowalla VerifyError. Can anyone tell me is there a fix for this? I have many product Reviews to do everyday and would like to carry on without wiping my device if possible? Thank you kindly