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

Native Development

Reply
New Contributor
Posts: 2
Registered: ‎07-10-2012
My Device: Simulator
My Carrier: Telenor

Error: Certificate chain not found for: RDK.

I tried to make debug token, and I followed this post:

 

http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/Playbook-cskpass-csjpass-cskpin-...

 

when I tried to proceed with point 6,

 

blackberry-signer -verbose -cskpass <your CSK password> 
-keystore <your P12 file> -storepass <your P12 file password>
<BAR_file.bar> RDK

 

I get 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.

 

what can I do to complete this process?

 

Thanks!

 

P.S.

I saw somewhere on forum, that I probably need new csj keys. I downloaded csj again, but now I got error:

 

Error: Already registered with PBDT

 

Maybe this is only solution, but, how to "clean" my computer, so I can install this new csj key?

 

Highlighted
Retired
Posts: 329
Registered: ‎05-07-2012
My Device: BB Alpha
My Carrier: N/A

Re: Error: Certificate chain not found for: RDK.

Retired
Posts: 329
Registered: ‎05-07-2012
My Device: BB Alpha
My Carrier: N/A

Re: Error: Certificate chain not found for: RDK.

Have you made any progress?

New Contributor
Posts: 4
Registered: ‎10-21-2012
My Device: Playbook
My Carrier: n/a

Re: Error: Certificate chain not found for: RDK.

I was having the same problem which seems to have been caused by having different author.p12 barsigner.csk and barsigner.db files spread across a number of different system directories: 

 

C:\Users\Stephen\AppData\Local\Research In Motion
C:\Users\Stephen\Local Settings\Application Data\Research In Motion
D:\Users\Stephen\Local Settings\Application Data\Research In Motion
D:\Users\Stephen\Research In Motion
 
I noticed the barsigner.db file in "D:\Users\Stephen\Research In Motion" seemed to be corrupt (0 byte size) so after restoring the keys from a backup to the "D:\Users\Stephen\Research In Motion" folder the ability to sign bar files and create debug tokens started working again.