Web and WebWorks Development

[WorkHorse]

I am trying to sign an app by following these instructions:

https://bdsc.webapps.blackberry.com/html5/documentation/ww_publishing/signing_setup_smartphone_apps_...

https://bdsc.webapps.blackberry.com/html5/documentation/ww_publishing/signing_your_smartphone_app_19...

I have done all the steps, and have tried packaging via both Ripple and command line to which I get successful finish messages:

I place the OTAInstall and StandardInstall folders from the output directory on my server and download and install the app. The icon shows up on the homescreen but when I click to launch it, it states that it cannot open because it is attempting to access a secure API. What am I doing wrong here I thought the signing process was complete? Or is this even related to the signing process? Any help would be appreciated, Thanks!

[TheSource]

Busy with the same problem.

Tried it with my app and a demo Hello World and no luck.

All csi keys are registered with RIM but no luck at all

[WorkHorse]

If you figure out a solution, give the a heads up I'm still having trouble with this.

[TheSource]

OK, got this working

Two things that I found on the forum.

1: The JDK needs to be 1.6, the SigTool is not supported by the latest JDK (1.7)

So I installed JDK 1.6. You need to change the following files:

C:\Program Files\Research in Motion\<BlackBerry SDK>\instalvarialbles.properties   and

C:\Program Files\Research in Motion\<BlackBerry SDK>\bin\bbwp.properties

Look for JAVA_HOME and update the path to you JDK 1.6

2: On Windows 7 the SigTool that comes with WebWorks for Smartphone v2.3 is buggy for some reason

To fix this you need to take the SigTool from a previous version (I took the SDK v2.2 SigTool) and replace it in the following folder

C:\Program Files\Research in Motion\<BlackBerry SDK>\bin\

The file you are looking for is SignatureTool

Once I made those changes I could package and sign my app. Installed to both the Bold 9700 and 9900 and no problems.

Hope this helps

[WorkHorse]

Hey thanks for the reply! Do you know which path I need to change it to? Would it be something like

C:\Program Files (x86)\Java\jre6\bin

or

C:\Program Files (x86)\Java\jre6\lib

or is this a completely different file path I'm not thinking about?

And secondly, is there a way to get the v2.2 Sigtool without reinstalling the 2.2 SDK, saving the Sigtool, then reverting back to 2.3 SDK and replacing it?

[WorkHorse]

My file path on instalvarialbles.properties is now:

JAVA_HOME=C\:\\Program Files (x86)\\Java\\jre6 

and

Java_Home=C\:\\Program Files (x86)\\Java\\jdk1.7.0_03

My file path on bbwp.properties is now:

<java>C:\Program Files (x86)\Java\jre6</java>

However when I run the same command as before to sign the app now, I get a 

 <bbwp.exe> Failed to find java.exe

I have also tried changing 

Java_Home=C\:\\Program Files (x86)\\Java\\jdk1.7.0_03

to

Java_Home=C\:\\Program Files (x86)\\Java\\jre6

without any luck. Am I inputing the correct paths?

[twindsor]

Pointing to the JRE is definitely not going to work. The packager is trying to compile a Java application.

You should be pointing to the JDK:

<java>C:\Program Files (x86)\Java\jdk1.6.0_27</java>

[WorkHorse]

Hey thanks twindsor for the post I got the app signing on jdk 1.6 now. However on the down side I'm still having the same issue. Pointing to 1.6 instead of 1.7 still signs the app on the command line as per the picture in the post but the launching the app on the bb still gives the same error. 

[twindsor · Accepted solution]

When it signs, what signatures are your cod files being signed with? Are you getting all of RBB, RCR, and RRT?

If you check the eventlog, you should see more information about the error that it's getting stuck on:

Hold Alt and press lglg on the device to see it, or run "Javaloader -u eventlog > log.txt" to pull it off to your computer.