05-14-2014 08:47 AM
Being new to BlackBerry but not to programming I wanted to create some apps but thats where the problem started:
I am not able to create a debug token.
Using Momentics IDE:
Pairing and Signing were successful.
The message I get is : "Error creating debug token"
Using the tools from usr\bin\
i was able to create the author.p12 file for signing with blackberry-keytool
But using blackberry-debugtokenrequest I was not able to create the debug token file. The syntax used is listed below (1). This tells me that devicepin could not be found.
Using (2) I get "Error: the specified csk password is not valid"
Adding -keystore "path of author.p12" changes nothing
Adding -cskpass "path of bbidtoken.csk file" results in the above error
Using the Token in the .csk file instead of the path the console does not finish the command and hangs-up. (Ctrl + C still works)
System is Win 8.1 x64 , Java is x86, used x86 powershell for the commands
If somebody can help, that would be really appreciated.
blackberry-debugtokenrequest -storepass <password> (-devicepin <device-pin>)+ [<options>] <debug-token-bar-file>
Solved! Go to Solution.
05-14-2014 11:16 AM - edited 05-14-2014 02:19 PM
The Help section to the command line part apparently just got (re)moved
Tried the following among othar variants now, but it did not work either:
.\blackberry-debugtokenrequest -storepass "myBBIDpassword" -devicepin myDeviceHexPin -cskpass "password for csk file" "f:\debug-token-bar-file.bar"
05-15-2014 02:29 AM
I'm using the old AIR SDK for creating debug tokens, but I'm also creating the tokens on command line, so the call should be similar. This is what I do
blackberry-debugtokenrequest -cskpass %1 -keystore %2 -storepass %3 -deviceId %4 newDebugToken.bar
%1 = password of the cskfile
%2 = your .p12 keystore
%3 = password of the keystore
%4 = hardware id of your device as hex (don't forget 0x)
also note that there are no ""
05-15-2014 06:53 AM
Thank you for the help. I adopted the syntax. However the error was still there. So I recreated the signing key(.csk). And it works now!
I think my older Password was too long, the jam site however threw no error. (Maybe cropped it without me knowing...)