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.
06-17-2013 04:49 AM
I know someone postet this before, but the issue was closed with no solution. I'm trying to convert and sign an apk to bar on a jenkins-build-server. I use a Script which works fine if i start it from the command-line but if i try starting it via jenkins I get the following error:
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.
Does anyone have a solution for this?
06-18-2013 02:52 PM
Is the Jenkins job running on the device that the key was registered to?
07-09-2013 06:07 AM
Hey guys, I ran into the same issue. The Jenkins server was executing the whole repackaging and signing stuff on a Windows Server machine. We fixed the issue by running the Jenkins Slave service as Administrator.