03-11-2011 11:16 AM
All,
I have hit a second problem with the key signing tool. I executed all the steps right up to the step named: "Ask the RIM Signing Authority to sign your BAR file". When I type in:
blackberry-signer -verbose -cskpass <your CSK password> -keystore <your P12 file> -storepass <your P12 file password> <BAR_file.bar> RDK
I get the following error:
barsigner error: developer certificate and private key not found in keystore or store password not supplied
I have triple checked my password, put the p12 key file in the same directory with the bar file and I have even tried registering p12 key with Windows. No joy.
Any suggestions?
Many thanks in advance guys,
H
03-11-2011 11:17 AM
What platform are you on? (You mention Windows but in a way that suggests you're not on it normally.)
Does your password contain punctuation? If so, try surrounding it with single quotes (not double-quotes), if you are on the Mac or Linux.
03-11-2011 11:20 AM
Sorry I am normally on Windows. No excuse from me on that one.
I am probably not supposed to say it but... nope, the password does not contain any punctuation.
Keep the suggestions coming,
H
03-11-2011 11:22 AM
Do any of the paths you are using in that command line include spaces? Generally with software development you're way better off never using spaces in paths. If you are, though, you always need quotation marks (double, this time) around them to avoid confusing the programs.
03-11-2011 11:31 AM
The strange thing is all the other steps worked. Otherwise, I shouldn't get a barsigner error.
Maybe I should grow up and use Linux someday...
H
03-12-2011 07:34 PM
I had the same error. I found a couple of things I was doing wrong and maybe they appy to you as well:
1. there is reference in the instructions to blackberry-tablet.xml and that the publisher name within that file has to be identical to what you used when you applied for keys + what you put in the command line. I am using CS5 and I have no idea what blackberry-tablet.xml is or what it contains. I found a reference somewhere that said you can get away without having a blackberry-tablet by putting:
-publisher "<your company name>"
as one of the parameters in the blackberry-airpackager command.
2. in the blackberry-keytool command, at the end it says -alias author, which I interpreted to mean putting the author name, but in fact you type it exactly as is (ie -alias author).
Good luck.
...Jim
03-28-2011 11:52 PM
JimmyO wrote:...2. in the blackberry-keytool command, at the end it says -alias author, which I interpreted to mean putting the author name, but in fact you type it exactly as is (ie -alias author).
Good luck.
...Jim
Turns out, that was the same issue I was having. Changing to -alias author did the trick. You however have to be careful with the cn name used in creating your sigtool.p12 file and the vendor name used when registering for keys as it is case sensitive.
Leon