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.
12-03-2012 01:44 PM
I've done some apps using WebWorks in the beginning of the year and they all signed fine. After 4 months without doing any BlackBerry development because I had other projects in other platforms I've returned, but now when I try to sign my applications I keep getting this error:
Nathan-Camposs-MacBook-Pro:BBApp Nathan$ /Developer/SDKs/Research\ In\ Motion/BlackBerry\ WebWorks\ SDK\ for\ TabletOS\ 18.104.22.168/bbwp/bbwp build/BBApp.zip -g ******** -buildId 1 -o build/ [INFO] Parsing command line options [ERROR] Cannot sign application - failed to find signing keys Nathan-Camposs-MacBook-Pro:BBApp Nathan$
I've tried using -cskdelete and registering new keys, it all worked and I received the emails from RIM that all my keys got registered successfully, but I'm still getting the same error after that. Anyone have a solution?
Solved! Go to Solution.
12-03-2012 02:32 PM - edited 12-03-2012 02:33 PM
Just to confirm (I'm assuming OSX here), can you please verify whether author.p12, barsigner.db, and barsigner.csk exist in the following folder:
~/Library/Research In Motion
If another OS, you can check the default folder here:
If you could provide a screenshot of that folder's contents, that would be ideal.
12-03-2012 02:41 PM
The blackberry-signer created the files inside ~/Research In Motion/:
This is the content of ~/Library/Research in Motion/:
I've tried copying the files to the directory you suggested and sadly I'm still getting the same error.
12-03-2012 04:53 PM
And just to confirm, do the contents of barsigner.db look similar to this:
#Do not edit manually. Generated automatically by RIM tools. #Thu Mar 15 17:22:48 EDT 2012 RDK=##########http\://www.rim.net/Websigner/servlet/RDK-Waterloo PBDT=##########http\://www.rim.net/Websigner/servlet/PBDT-Waterloo
Note that ########## will correspond to your own client ID. The important part is that both RDK and PBDT are referenced in this file.
12-03-2012 05:04 PM
12-03-2012 05:37 PM
12-03-2012 05:47 PM
12-03-2012 05:54 PM
Another check, are all three signing files greater than 0kb? barsigner.db would have to be if its contents matched the previous example, but can you please confirm whether author.p12 and barsigner.csk are also both over 0kb in size?
There was a previous instance of some corrupt signing files that resulted in the the same errors a while back it seems.
12-03-2012 06:33 PM
12-04-2012 11:46 AM
Let's give this another try :-) Can you confirm where your home directory is set? There is a guide on changing your home directory here:
Note that we don't need to change anything, we just want to confirm the value that is assigned to your home directory. The tools themselves would be using the ~ path to attempt locating your signature keys, and if that path has been modified, then that may explain why it can't find your keys (i.e. it is looking elsewhere.)