05-12-2011 05:30 PM
I followed the instruction to the letter from here:
and I've got the keystore setup properly and the PlayBook signing key installed and goten a message: succesfully registered.
I also register the PlayBook Debug Token key and had gotten registered succesfull.
When I now try to generate a debugtoken for my PlayBook using the following command line:
Solved! Go to Solution.
05-17-2011 05:56 AM
05-18-2011 06:08 PM - edited 05-18-2011 06:10 PM
I am getting exactly the same error can anyone help?
(The only difference is that I am trying to dev using AIR)
I have double check/triple checked the passwords for -cskpass & -storepass are correct
as is -keystore location for the .p12
RIM? It is your new Baby, you have to help us Dev's if you want to pull it off!
05-27-2011 03:51 AM
06-06-2011 01:14 PM
Dennis - where is your sigtool.p12 file stored?
Is it in the same directory as where you are running that command from? If not can you try including the full system path to the sigtool.p12 file and let me know if that resolves this error?
C:\Program Files\Research In Motion\BlackBerry WebWorks SDK for TabletOS 126.96.36.199\bbwp\bin\sigtool.p12
06-07-2011 03:28 PM - edited 06-07-2011 04:16 PM
I've got the sigtool.p12 stored currently within the same directory as where I start the command line, which is:
/Users/dennisreumer/Developer/SDKs/Research In Motion/bbwp/blackberry-tablet-sdk/bin
I've been succesful in creating the Key store, registering the signing keys and specifically register the debug key for debugging purposes, without any errors.
So I should know the passwords to the store and keys (used the same to register the keys off course.)
Even tried a sudo of the command, same result (just to exclude any access rights for the files).
changing anything in the name of the sig file gives me a different error:
debugtokenrequest error: keystore load: /Users/dennisreumer/Developer/SDKs/Research In Motion/bbwp/blackberry-tablet-sdk/bin/sigtool1.p12 (No such file or directory)
changing the password also gives me a different error:
debugtokenrequest error: keystore load: failed to decrypt safe contents entry: javax.crypto.BadPaddingException: Given final block not properly padded
Which makes me believe the sigtool.p12 file location and its pasword are correct.
Which would leave me with the -cskpass option that is at fault, which would be very strange as I had succesful registered the signing and debug token keys using the same password.
the path of the barsigner.csk and barsigner.db is
/Users/dennisreumer/Library/Research In Motion
(as was default installed by the WebSDK installer).
Also tried to move them to:
/Library/Research In Motion (root to Harddisk)
So I'm running on fumes now.
06-09-2011 11:23 AM
I just had the same problem here and found that the alias in your keystore MUST be author : http://docs.blackberry.com/en/developers/deliverab
You can see the current name with
Keystore type: PKCS12Keystore provider: SunJSSE
Your keystore contains 1 entry
cardiweb, 9 juin 2011, PrivateKeyEntry,Certificate fingerprint (MD5): DD:22:9B:CF:E9:F3:54:7A:F3:0D:96:C9:61:FE:6A:89
And you can rename it with
06-10-2011 10:14 AM
Right that author part did it.
Many thanks !!!
./blackberry-keytool -genkeypair -keystore archeit.p12 -storepass xxxxxxxx -dname "cn=Arche IT bv" -alias author
But i did this:
./blackberry-keytool -genkeypair -keystore archeit.p12 -storepass xxxxxxxx -dname "cn=Arche IT bv" -alias reumerd
As I'm the author
06-10-2011 10:23 AM
I did the same mistake. The doc should be more explicit and explain that 'author' is mandatory.
But did you finally succeed in signing and deploying your app ?
Because I think that, as for author, the keystore MUST be called "sigtool.p12" because when using bbwp for signing you can't tell which p12 to use
06-20-2011 04:58 PM
Very happy to hear you were able to resolve this. Unfortunate it took so long, and I'll admit a problem like this should not even be yours to deal with.
I have escalated a suggestion to our Documentation team to highlight the requirement of the literal value (and not substitute your own values in place of "author").
mbaroukh - you are correct, you must specify your signing key file name as "sigtool.p12".