05-18-2011 07:16 PM
I am a Mac & FDT user, as a result I need to create tokens etc via Terminal
So far I have:
Successfully created a CSK file using:
./blackberry-signer -csksetup -cskpass <myPassword>
CSK file created.
Then following the instructions from here:
I have registered my CSJ registration file:
blackberry-debugtokenrequest -register -cskpass <myPassword> -csjpin <myCSJ_PIN> </Users/Home/_keys/client-PBDT-01234567890.csj>
Successfully registered with server.
Next I attempt to generate a debug_token.bar for my PlayBook using the following command line:
./blackberry-debugtokenrequest -cskpass <myPassword> -keystore /Users/Home/_keys/RIM/blackberryDevCert.p12 -storepass <myPassword> -deviceId 0x<playbookPIN> /Users/Home/_keys/RIM/debug_token.bar
I get the following error:
debugtokenrequest error: Can't find resource for bundle net.rim.device.codesigning.debugtoken.DebugTokenRe
I have double check/triple checked the passwords for -cskpass & -storepass are correct as is -keystore location for the .p12
Incidentally the password for cskpass & storepass are the same, but I can't imagine that would be an issue.
Could someone please explain where I have gone wrong?
05-19-2011 03:11 AM
I would also like to add that I used the tutorial on this page to double check that I entered everything correctly:
Does anyone have any advice?
05-19-2011 08:43 AM
Did you register both CSJ files you were sent? They would have been sent in two different email messages. One would have RDK in the filename and the other PBDT. The first is used for signing an application, the second for creating debug tokens.
05-19-2011 11:04 AM - edited 05-19-2011 11:06 AM
Thanks for getting back to me
Yes, I have registered my DebugToken .csj using:
./blackberry-debugtokenrequest -register -cskpass <myPassword> -csjpin <myPassword> /Users/Home/_keys/RIM/client-PBDT-01234567890.csj
Successfully registered with server.
And for the RDK .csj I entered:
./blackberry-signer -register -csjpin <myPassword> -cskpass <myPassword> /Users/Home/_keys/RIM/client-RDK-01234567890.csj
The first time there was no server response, upon entering it again I saw:
barsigner error: already registered with RDK
Which lead me to the conclusion that it must have successfully registered with server.
05-19-2011 01:10 PM
When you created your developer certificate (the .p12 file) did you specify "author" in the -author parameter?
05-19-2011 07:16 PM - edited 05-19-2011 07:23 PM
it appears I didn't use -author , I used -alias entered in the following format
./blackberry-keytool -genkeypair -keystore /Users/Home/_keys/RIM/blackberryDevCert.p12 -storepass <myPassword> -dname "cn=****" -alias Firstname Lastname
keytool error: java.lang.RuntimeException: Usage error, Lastname is not a legal command
./blackberry-keytool -genkeypair -keystore /Users/Home/_keys/RIM/blackberryDevCert.p12 -storepass <myPassword> -dname "cn=****" -alias "Firstname Lastname"
// output: This appeared to be successful as a .p12 was created
The directions on http://docs.blackberry.com/en/developers/deliverab
blackberry-keytool -genkeypair -keystore <output_file.p12>
-storepass <create_a_password> -dname "cn=<company_name>" -alias author
So is the documentation incorrect?
Did I do something wrong?
05-20-2011 09:22 AM
blackberry-keytool -genkeypair -keystore <output_file.p12> -storepass <create_a_password> -dname "cn=<company_name>" -alias author
The documentation is correct here, but note that you only replace the parameters with <>. -alias author should remain as is (you need to use author).
05-20-2011 09:50 AM
So you are telling me I actually need to enter:
./blackberry-keytool -genkeypair -keystore /Users/Home/_keys/RIM/blackberryDevCert.p12 -storepass <myPassword> -dname "cn=****" -alias author
If so I can attempt this again in a few hours
05-20-2011 10:24 AM
05-20-2011 07:27 PM - edited 05-20-2011 07:28 PM
Mark, thank you! that works nicely now!
I have used Richard Lords ANT Build files to help me build/deploy my test app.
And just a pointer to others reading this thread, dont forget to launch a terminal window for debugging:
once launched type run at the (fdb) prompt:
then once connected to the SWF on the Playbook type continue at the (fdb) prompt, so: