12-08-2011 10:22 AM
I am developing a BlackBerry application for my dissertation, which I need to test by loading onto my device. I've received the keys from RIM but am getting the 'Not Registered' message when trying to sign with the Runtime API key.
From what I have read online, I would be needed to pay $100 to deploy it onto the device using the restricted API's that I'm using (mainly access to the RMS) This app will only ever need loading onto my single device, which I assumed could be done easily and FOC, as it would never reach the public domain?!
Is there a way to do this?
Solved! Go to Solution.
12-08-2011 05:07 PM
There is no way around code signing, but the good news is that code signing keys are now free. Just fill out the form below to request your own keys.
12-08-2011 07:19 PM
Thanks for your reply - I'm glad to hear that it's free!
I already have the signing keys for my device (loaded into eclipse). However when I go to sign using the signature tool, it says "Not Registered" next to the RRT (RIM Runtime API) key, and fails to fully sign the COD file.
The other 2 keys sign correctly - how do I go about signing for the Runtime API
Thanks in advance!
12-09-2011 09:05 AM
Make sure you install all 3 CSI files that were sent to you. It looks like you have only installed 2 of the 3 required keys.
12-09-2011 11:01 AM
I have all the 3 CSI files installed and am finding that the Signature Tool is hanging/crashing at the 'Receiving Response' stage of the signing. This only happens for the Runtime API, the others succeed.
I researched this and saw a message saying that version 7 of the JDK was at fault, however after removing this and installing version 6 (update 29, 64-bit) and restarting, the issue persists. Are there any other known workarounds? I still have v7 of the JRE, if this is also known to be at fault?
12-09-2011 11:10 AM
I recommend removing the 7.0 JRE as well. It appears that SignatureTool is using it.