Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
04-21-2010 11:05 PM - edited 04-21-2010 11:06 PM
Anyone else had problems with the eclipse plugin and signing keys?
I'm running plugin version 18.104.22.168003212304-12 with eclipse 3.5.2
This version has the rather nice feature of being able to package and sign in one go. Except when signing, on my workstation at least, it is unable to locate a perfectly valid set of keys and therefore refuses to sign anything.
And subsequently I can't sign manually in eclipse either.
I'm having to run the signing tool from the command line to sign my apps.
Solved! Go to Solution.
04-22-2010 12:06 AM
In Eclipse, open up Window>Preferences, then select BlackBerry Java Plug-in>Signature Tool and click on "Import Existing Keys...". Navigate to the folder that has the keys data base that the command line is using (usually a folder containing sigtool.csk and sigtool.db) and you should be good to go.
04-22-2010 12:48 AM
Already tried that (several times) but the plug in refuses to recognize my keys.
But oddly enough it then prompts for my password, and fails to sign the cod files.
I've requested replacement keys so I can import from new to see if that works, but unfortunately there appears to be a backlog. Not sure why the key issue isn't automatic, but if it creates jobs I suppose I shouldn't complain.
The latest changes to the plug in also messed up my deploy scripts, which will now have to be completely rewritten. Just like last time the plugin was updated.
The joys of BlackBerry development.
04-22-2010 01:13 AM
My sympathies. No idea why it didn't work for you, though. That's the process I used when I upgraded the plug-in. What does say when it refuses to recognize the keys?
04-22-2010 08:50 AM
I was experiencing the same problem. After upgrading the plug-in to 22.214.171.124003212304-12, I imported my signing keys. But when I tried to sign my app, I was asked: “Please enter your private key password , and re-encrypt your private key information file.” After that I got, “The private key is not located in the sigtool.csk file”.
I noticed a new folder under my eclipse install that wasn't there before the upgrade: .\plugins\net.rim.ejde\vmTools. The sigtool.csk and sigtool.db files in this folder both had a zero length. So I copied the files from the old folder, .\plugins\net.rim.ejde\signTool, and now my key signing works as it did before.
Hope that helps someone else.
04-22-2010 01:56 PM
thank you for the note, I've had the same problem, but was not able to find where did the signature files go.
I had same problem as guys wrote above...
01-21-2011 02:55 PM
It works great. Thanks for the advice.
Originally I had my signature keys in Blackberry Eclipse Plugin 126.96.36.199. But finally I can migrate them to the new Plugin.
Greetings form Mexico