02-15-2012 04:01 PM
On AIR SDK development to sign a key for .bar file
blackberry-signer -verbose -cskpass <keypasswd> -keystore author.p12 -storepass <keypasswd> specific_file.bar RDK
blackberry-signer -keystore author.p12 -storepass <keypasswd> specific_file.bar author
After using the same commands for Native SDK's .bar file, .RDK files cannot be generated.
.bar file is generated via QNX_momentics_IDE/export/build realese.
Does anyone know how to sign a key on .bar file for Native SDK application?
Thanks your attention.
Solved! Go to Solution.
02-15-2012 04:12 PM
This file is already signed if you check "Sign" when doing export. Otherwise it is same command (but if you try to sign debbug bar file it will fail because it is development mode)
02-15-2012 04:32 PM
When I use digital sign, error is coming out.
Error: Unable to sign bar: Server is not responding.
Please make sure your proxy settings are correct, if applicable. Supply the following options to barsigner:
-proxyhost <host> - proxy host
-proxyport <port> - port number for connecting to the proxy host
-proxyusername <username> - username for the proxy host (optional)
-proxypassword <password> - password for the proxy host (optional)
(Time of error: 15 February, 2012 4:31:26 PM ES
After I check proxy host, port, username, password, I could not find what's wrong.
02-15-2012 04:42 PM
Hmm. Air signing tools are exactly the same, if you can sign from air - just try to use same command lines (from the air installation)
a) Export release from IDE but uncheck signing
b) Sign from command line
02-15-2012 04:48 PM
When I use the command to sign .bar file, RDK file cannot be generated in .bar. ??
Still thank you to verify my action.
02-15-2012 04:53 PM
blackberry-signer -verbose -cskpass -keystore author.p12 -storepass HelloWorldDisplay.bar RDK
The command can work on AIR's .bar file.
02-16-2012 09:15 AM
Current error code changes to the RIM server error??
Error: Server returned HTTP response code: 502 for URL: http://www.rim.net/Websigner/servlet/RDK-Waterloo
(Time of error: 16 February, 2012 9:13:26 AM ES