Web and WebWorks Development

[zahirw]

I've applied for and received the signing keys from RIM however, when I try signing the keys using the following command

java -jar SignatureTool.jar <.csi file path>

However, it keeps giving me an error saying that the sigtool file is missing and asks me to create a new password.

I'm specifying the correct path for the csi file

Thanks

[Ranaman]

Pull everything into one directory and try it out then... Silly suggestion I know, but better to start small...

[zahirw]

Tried that. Had no impact...

[ignites]

file path needs to include the file name and extension. try that. 

[zahirw]

Yes, did that from the get go.

[zahirw]

I'm really stuck here because I can't test the app on my phone.

I tried ripple's publish feature but before it signs the app, I need to have the signature tool validate the csi files.

The signature tool simply ignores the csi files.

Am I doing something wrong? Can't I directly sign the app using ripple?

[Ranaman]

Can you include a screenshot? 

(This suggestion sucks, but starting over by dowloading the SDK again along with requesting new keys may be your next step...)

https://bdsc.webapps.blackberry.com/html5/documentation/signing_landing_page.html

[zahirw]

Actually I signed up for new keys. It also seems that the .csk file is missing from the bin folder and I have no idea as to where I can fiind or download it.

Whenever I try and sign the keys, it tells me that the csk file is missing and simply ignores the csi file asking me to create a new file & sign the cod.

If I'm correct, the once I sign the csi files using the sigtool, I can then directly build & publish via ripple correct?

[Ranaman]

Yup. Ripple has build, package and sign...

http://www.youtube.com/watch?v=HEbrieh4ibg

[astanley]

The CSK file is generated by the SignatureTool.jar file when you ran the command to install the *.CSI files that were emailed to you.  

To simplify it - suggest saving the *.csi files into the /bbwp/bin installation folder of the WebWorks SDK (the SignatureTool.bar file should exist in this folder).  Then install these keys using the command you listed in your first post, and you should see a sigtool.csk file created in the same folder. 

At this point, you should be able to properly sign your apps because the SigTool app knows where it can find the CSK file (in the same folder as itself).

Make sense?