07-18-2013 03:08 AM
i have submit my app to app world and after i got the mail of While testing your app on the BlackBerry Smartphones 8520, 8530, 9300, 9330, 9860, 9850, 9360, 9350 and 9800 gives message "Error starting Pbar2: Module 'Pbar2-3' attempts to access a secure API".
i have signed my app with keys properly plz guide me
Solved! Go to Solution.
07-18-2013 03:12 AM
07-19-2013 04:36 AM
Definitely signed and is using all 3 keys correctly. Now you need to make sure that this is the cod (cods) that are on device. The easiest thing to to do is go into Options, Applications, then use the Menu to access 'Modules'. In the module list, look for your modules. Click on the modules in the list and the information provided should indicate a timestamp and whether they are signed or not. Make sure the time stamp matches what you expect and they are signed. I suspect they are not and there is an issue in the process you use to get these to the device.
07-20-2013 02:02 AM
hi.., i have found the following error .., i think this is very important ,plz guide me where i'm wrong
module 24904 cannot reference net.rim.device.api.system.PersistentStore [52237.375] Module 'Pbar2-3' attempts to access a secure API.[52237.375] [52237.375] Linker error: 'VerifyError' for Pbar2 [52237.453] VM:CLRCv=0 [52237.586] VM:RCTCv=1266,w=1294 [52237.594] FS: CLEAN(1604 5) [52243.727] CMM: set CRC e1449c80 [52243.727] NVS: delete 2 [52243.727] NVS: write 2 [52243.727] NVS: erase 2253 [52243.727] NVS: commit 622 [52243.875] AM: Error starting Pbar2: Module 'Pbar2-3' attempts to access a secure API.
07-20-2013 05:05 AM
As noted in my previos post "Now you need to make sure that this is the cod (cods) that are on device. "
So look for the modules,, look for the signing details and date/time that you can find for each modele, specifically checking Pbar2-3.cod.
07-20-2013 05:57 AM
The cod files will also display the signing keys used, have you checked that all three keys have been applied to that cod.
There was something odd about your signing, and that was there were no optional signatures. I have never coded anything that did not have optional signatures. So perhaps there is a problem with the signing tool.
To check, I would 'unzip' the Pbar2 cod file into its indivdual cods. Then start the signing tool, and point if at each individual cod. It will probably complain about a missing csl/cso file, but I think it will still tell you if the cods are signed or not.
You can run the Signature Tool directly, just find
and double click on it, presumably java will have indicated that it should run jars and it will start up. Then click 'add' and browse to the place you have unzipped the cod to.
If this doesn't help, attach the failing application here and I (or someone else) can check it out.