02-20-2009 12:21 PM
I am trying to codesign my first app that has required it. I have got the csi files from RIM and registered them without any problems, but when I go into the Signature tool, choose the .cod that needs signing and click request I get this error. What does it mean, and how would I go about registering my application with the signing authorities. The user guide talks about finding the .cod files and then double clicking on them to attach the signatures (csl files), but on my PC, the .cod extension has been associated with MS Visual Studio which clearly isn't a lot of use in this process. Anybody able to help?
Solved! Go to Solution.
02-23-2009 09:29 PM
I'm running into this same issue. I have received my three .CSI files, and I have signed them successfully. But, when I open Eclipse and go to BlackBerry >> Request Signatures, then I select the appropriate record in the table and click the "Request Signatures" button I get the error: "Unable to request signatures until this application has been registered..."
If anyone has any information I would appreciate it.
02-24-2009 11:24 AM
OK. I have managed to get this one sussed (well sort of). Firstly, I am running vista and installed a Visual Studio component after installing the JDE. This re-assigned the file association for .cod files and however much I tried to re-install the JDE, it didn't get put back. Vista is a bit obtuse in that the sensible file association process that used to be possible on XP (the file types tab under folder options) no longer exists and it is only possible from the GUI to assign a file type to an executable, not a complex command line. Apparently there are tools that do let you do it, or you can resort to changing registry settings. Good luck!
The compounding problem is that I have also installed both the JDE and the eclipse plug in on the same machine and it appears that they both have their own version of the signature tool. Because I installed the JDE last, when I double clicked on the .csi files, the code signing certificate and key has been placed in the bin directory of the JDE. The eclipse plug in code signing tool doesn't see that it is there and therfore tells me that it has not been registered. I can't for the life of me find out where the eclipse plug in signaturetool.jar is to try and fix this, so I have given up.
However, I can now sign my applications. All I have had to do is to create a shortcut on my desktop to run the JDE version of the signaturetool.jar and then when it opens, navigate to the location of the .cod files in the eclipse workspace and voila, I can sign the cod's.
One day I might just rebuild PC with XP and only install the eclipse plug in, but then I will have the nightmare of migrating the signature registration. Hang it. I'll just stick with what is working.
02-24-2009 11:33 AM
02-27-2009 11:03 AM
The BlackBerry JDE Plug-in for Eclipse stores the SignatureTool.jar and keys in the following directory.
02-27-2009 12:09 PM
Thanks for your response but I've figured out the problem in the meantime, with a little help from the BB Support.
I have the JDE Eclipse Plug-In AND the stand-alone JDE installed. When I signed my keys, all the necessary files where placed in the BIN directory of the stand-alone JDE. Once I copied the appropriate files into the plug-in\bin directory, everything was smooth sailing.
One thing I noticed about the SigTool (from inside Eclipse) is that the records are red if the keys can't be found, blue if the keys are found but the application hasn't been registered.
03-15-2009 10:38 AM
I'm having same problem but in reverse.. I started with Eclipse and now going to BB JDE.
Can someone tell me exactly what files were copied?
I see SignatureTool.jar, sigtool.set and sigtool.bat in the bin directories.
I also see a .cso and a .csl in the Eclipse project directory
04-13-2009 10:13 AM
My problem was that I have the standalone JDE installed on M$ Vista. Vista saves files that an application creates in the user's AppData folder, not the Program Files/... folder. Thus by coping the sigtool.csk and sigtool.db from
c:\Program Files\Research In Motion\BlackBerry JDE 4.6.1\bin\
and ran the SignatureTool.jar, all worked