09-08-2008 01:41 AM
Hello and thanks in advance for taking the time to read and hopefully answer this question.
I've been able to sign and load my app onto my 8330. However, when I try to run the application, I receive an error message saying that one of my modules/libraries must be signed with the RRT key.
However, when I click on the cod file for the module, it only wants to sign the module with the RBB and RCR keys.
I've applied for and received the csi files from RIM. I successfully registered the keys with RIM.
Inside the Signature tool, I have 3 registered signers, RBB, RRT and RCR. I've been able to successfully sign a test application with all 3 keys.
I'm using JDE 4.5.0 and I'm loading the application onto a 8330.
My main application is in a package "com.me.app" and my libraries are in a package "com.me.lib.a".
Both projects, "com.me.app" and "com.me.lib.a" are active. The project "com.me.app" is marked as a CDLC application with a project dependency on "com.me.lib.a". Project "com.me.app" also includes the jar file and the alx file from "com.me.lib.a".
The project "com.me.lib.a" is marked as a library.
How do I make the Signature tool sign the library with the RRT key which the device says I need before it will load the module?
09-08-2008 02:02 AM
I am not sure that is the root of the problem. But check that.
When you declare some class Persistable some IDE's offer you to import one of two classes.
The first import (with vm name in package) leads to problems with signing the application. Make sure that you have imported
when you declared a class as Persistable
09-08-2008 10:15 AM
rafo, thanks for the fast response.
I search the source code and I am not using any classes that have "vm" in the package name.
I also tried using very simple package names, just in case it was my naming schema that messed stuff up. I still run into the same issue.
What else should I be checking?
09-08-2008 11:27 AM
Are the library jar files being built by the BlackBerry JDE or have they already been built in another IDE?
You can verify what keys a cod file has been signed with by opening up the cod file(s) using the SignatureTool.
09-08-2008 11:38 AM
Decompose your problem to the smaller tasks and consider each of them closely.
What about signing the library cod file?
What about external jar-file. What classes have you used to compose this jar file.
To be sure that you have correct signing keys - try to write simple hello world application and sign it.
09-08-2008 11:40 AM
Hello Mark. Thanks for the response.
The jar files are being built by the BlackBerry JDE.
When I open up the library files (double click on the cod file) in the SignatureTool, the libraries are only signed with the RBB and RCR keys.
09-08-2008 11:48 AM
Good points rafo.
>What about signing the library cod file?
As far as I can tell, I cannot force the SignatureTool to use a particular key. It's automatically determined. As I've previously posted, when I inspected the cod file with the SignatureTool, I'm missing the key that the device is complaining about (makes perfect sense).
>What about external jar-file. What classes have you used to compose this jar file.
I'm not sure what you are referring to here. I don't explicitly import any jar files into the library. I'm trying to use as many RIM APIs as I can and then any other ones documented in the JDE documentation. I don't try to load any external jar files into my code.
I'm importing the following classes in the library:
>To be sure that you have correct signing keys - try to write simple hello world application and sign it.
I've tested this already and the main app is signed correctly.
09-08-2008 12:10 PM
Very strange picture.
I suggest the following way.
Create a new clean JDE project. And add step by step to this project classes from your library that does not want to be signed properly.
After adding every class - try to sign the library.
If after adding a class to the library you get a problem with signing - inspect this class very closely and show this class here.
09-08-2008 02:07 PM
09-09-2008 08:35 AM
Thanks rafo and Mark for all your help.
Mark, I just have version 4.5.0 of the JDE installed.
I was poking around last night, and I *think* I know what is the cause of the issue. For whatever reason, the JDE is not generating a .csl file for any project that I create.
I copied a .csl file from a project that had it, renamed it to the project name of the library and now the SignatureTool has the keys that I want.
So here's the question, why is the JDE not generating .csl files for new projects anymore?