06-07-2012 11:52 AM
I'm using the latest version of the BB10 WebWorks SDK (1.0.0.15) and am trying to configure my system (Mac OS X) for signing and debug tokens. I have previously setup my system for BB OS 5+ signing successfully. I have not previously configured my system for PlayBook signing. When I attempt to run the blackberry-signer from the command line I am receiving an error that author.p12 does not exist which is confusing since I thought blackberry-signer was suppose to create it:
$ ./blackberry-signer register -csjpin mypin -storepass mypass pathtoRDK.csj pathtoPBDT.csj
Enter Passphrase for keystore:
Error: Keystore load: /Users/myuser/Library/Research In Motion/author.p12 (No such file or directory)
Specifying the verbose flag does not produce any additional information. Anyone know what is going on?
Solved! Go to Solution.
06-08-2012 03:13 PM
The documentation has a "-register", not "register"?
I find it easier to use our Graphical Tool: http://supportforums.blackberry.com/t5/Testing-and
06-08-2012 04:25 PM
Wow, can't believe I didn't realize I left the '-' off of the register command. In my defense, the argument checking probably could be enhanced and a better error message thrown. Thanks, after fixing my user error it worked!
06-08-2012 04:28 PM
Totally understand. That's why I always use the graphical tool myself ![]()
08-13-2012 05:09 AM
twindsor wrote:
Totally understand. That's why I always use the graphical tool myself
Hi Tim. I would like to use the Graphical Tool myself, but is it already useable for BB10 SDK? When using the command line or Ripple 0.9.7 to sign for BB10 I always get the error reported here: http://supportforums.blackberry.com/t5/Testing-and
I researched the topics available in the forum but couldn't find the problem causing the error until now. On PB it is working really well using the PB SDK, but using the BB10 SDK signing fails every time, I can only use debug token to get it up running on the device for testing purposes.
08-27-2012 05:30 PM
That issue is outside of my expertise. I'd suggest going through our code signing help wizard and requesting to open a ticket. One of our code signing experts can help you out.
https://bdsc.webapps.blackberry.com/CodeSigningHel