[lorennorman]

Now when i try to run my program, utilizing the third party API jar for the printer/cardreader, i receive an error stating:

Error starting MyProgram: Module 'MyProgram' must be signed with the RIM Runtime Code Signing Key (RRT).

So, how do i get one of those?

[simon.hain]

you can buy them from RIM. they are us$ 100 for each client.
without a key you can not access "signed" elements.

gs
simon

[lorennorman]

Ok, so i got the Signing Authority Tool. I run the File Signer on my .cod file. It sends the info to RIM and returns a signature, everything looks to be fine. I deploy the new .cod file to my BlackBerry, and receive the same message "...must be signed with the RIM Runtime Code Signing Key (RRT)."

So, are there different file signers? I don't see any other way to sign this file, and i seem to be successfully signing it with the tool, so why is it still telling me it needs to be signed? Do i need special signatures to use certain APIs?

Confusion abounds...

[wss]

In my experience sometimes signed cod's still give this error. try deleting the cod's, rebuilding, resigning and reloading. can be frustrating. should work eventually.

[lorennorman]

I'm seeing now through the JDE that it is signing 2 of 3 items, but the one says

"Status: Not Registered; Category: Required; SignerID: 3; Signer Name: RIMAPPSA2"

Seems like i need to register with this signer to get signatures for this item, but i don't really have any information to go on. SignerID: 3? What is that? And RIMAPPSA2 doesn't return anything useful on Google... help?

[patrickh]

Check
http://www.blackberry.com/developers.../jde/api.shtml

[richever]

I just went through the same thing as you. I requested from RIM the ability to sign my code and submitted to them $100. I got an email with 3 files attached. The developer's guide, volume 2, page 10, tells you to 'Double-click a .csi file' and follow the remaining steps. But, you still need to do the same thing for the remaining files you get from RIM. They were good enough to *not* tell you this. What I did was manually run the signature tool on the remaining two .csi files. I think you can double-click them, too. I can't recall but a dialog appeared warning me that by proceeding I will overwrite some data. I disregarded this and everything still worked out fine.

Hope this helps!

Rich

[lorennorman]

Thanks, it seems to me that there is a difference in downloading the Signing Authority Tool and simply letting the one in the JDE do the work? I'm not sure, but i downloaded the tool first and i was faced with options that didn't seem to make sense, and i was signing applications with arbitrary keys (ie whatever i put in as a SignerID when i registered the product) but all of that seems wrong, because i want to sign my code to the RRT thing which is RIM specific. It seems like those .csi files are what i need, and they plug into the JDE to correctly sign code, and i don't need this standalone filesigner at all.

At any rate, i haven't tried this out yet because RIM only lets you register with the keys once, so, when i wiped out everything and reinstalled, they won't let me register again, so i'm waiting on new keys. (sigh)

Hope i'm on the right track, guess i'll know tomorrow. More help appreciated if you know any of my response here to be correct or incorrect!

Thanks,
Loren

[richever]

I think the tool you download is meant for those with JDEs prior to version 4.0. The SignatureTool is included in later versions. Its jar file is located in the bin directory under the JDE install directory.

I'm using JDE 4.1.0 and I didn't have to down load anthing extra. How this tool is used from the command line is described in the dev guide, vol 2. The JDE can also be used to sign code (your .cod files) by selecting Build -> Request Signatures.... This process is also described in the dev guide.

Sorry you have to wait for keys again.

Rich

[bbCincinnati]

In response to lorennorman's post of 01-16-2006 10:50 AM:
-------------------------------------------------------------------------

I believe I was having a similar problem. I had the Signing Tool registered and had successfully distributed several applications to my Blackberry. But then, with one of my applications, when I double-clicked the .cod file to request a signature, I noticed that one the lines read:

Status: Not Registered
Category: Required
SignerID: 3
Signer Name: RIMAPPSA2

In the details it said:

"Please contact the signer and register with the Signing Authority".


Here was my problem:
--------------------------------
When trying to use the Persistable Interface, I was trying to:

import net.rim.vm.Persistable; // <--THIS SEEMS TO BE CAUSING THE PROBLEM.


Solution:
----------------
When I looked it up again in the Javadocs, I saw that I should have been using:

import net.rim.device.api.util.*; // <--USING THIS INSTEAD SEEMED TO FIX IT.


Anyway, now it seems to load and run on the Blackberry ok.

Hopefully this might help someone in the future

[cool dude]

would any of you be interested in signing an small application for me. I could pay a small fee to recoupe your us$100

It just needs the RRT element signed.

[jfisher]

no. it's not a monetary thing, the codesigning keys let rim trackback if any malicious software appears in the wild and narrow it down to which company created it - there's a lot of agreements you sign when you signup and i'm pretty sure there'll be a clause that doesn't allow it.

[suribabuas]

Hi All,

I got the .csi files from RIM. When i tried to register those files it shows the alert messages like,,,,,The private key could not be found,and The private key is contained in the sigtool.csk which was not found.
Expected location:c:/blackberryjde4.2\binsigtool.csk.

when i press Yes. It doesnt shows nothing. what i will do. help me . please

Thanks,
suresh a