Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Web and WebWorks Development


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.


Reply
Developer
Posts: 33
Registered: ‎03-04-2011
My Device: PlayBook
Accepted Solution

Transferring keys to a new computer

Hello,

 

I am looking to sign PlayBook apps on a new computer. I've installed the WebWorks for PlayBook SDK, and transferred over sigtool.p12 to /bbwp/bin. I've also copied barsigner.csk to ~/Library/Research In Motion/.

 

Unfortunately when signing applications I now receive the following error:

 

barsigner error: Certificate chain not found for: RDK.  RDK must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain.

 

How do I solve this? I do not mind requesting new keys if need be, but would this prevent current users of my app from updating?

 

Thanks!

Highlighted
Developer
Posts: 163
Registered: ‎05-06-2011
My Device: Playbook
My Carrier: Not Specified

Re: Transferring keys to a new computer

Developer
Posts: 33
Registered: ‎03-04-2011
My Device: PlayBook

Re: Transferring keys to a new computer

[ Edited ]

Hi Praveen,

 

Thank you for your reply. I've carried out the instructions in the document and the same error occurs. Note that the packager doesn't even attempt to sign unless sigtool.p12 is in /bbwp/bin/ ("Cannot sign application - failed to find signing keys").

 

Any ideas? I need to sign my apps urgently. Will signing with new keys cause problems for my install base?

 

Edit: There is no barsigner.db file present in the backup of my old machine. Could this be related to the previous SDK being the beta?

Developer
Posts: 163
Registered: ‎05-06-2011
My Device: Playbook
My Carrier: Not Specified

Re: Transferring keys to a new computer

I'm not sure if its the beta issue. Try creating a file barsigner.db with the following contents. Replace the X with the no present in your CSK files. Not sure if this will work out. Give it a try. Else you could sign it with new set of keys.

 

#Do not edit manually.  Generated automatically by RIM tools.
RDK=XXXXXXXXXXhttp\://www.rim.net/Websigner/servlet/RDK-Waterloo
PBDT=XXXXXXXXXXhttp\://www.rim.net/Websigner/servlet/PBDT-Waterloo

 

Developer
Posts: 33
Registered: ‎03-04-2011
My Device: PlayBook

Re: Transferring keys to a new computer

That fixed it, thank you! For anyone else having the same problem, the number you need is "client-RDK-xxxxxxxxx.csj".