08-17-2012 03:11 PM
b10/fivedice.zip -o /Users/rory/Documents/git/BB_Apps/fivedice/build/b b10 -g <mypass> --buildId 53 [INFO] Populating application source [INFO] Parsing config.xml [INFO] Generating output files [INFO] Info: Package created: /Users/rory/Documents/git/BB_Apps/fivedice/build/b b10/simulator/fivedice.bar [INFO] Info: Package created: /Users/rory/Documents/git/BB_Apps/fivedice/build/b b10/device/fivedice.bar [INFO] execvp(): No such file or directory
Could there be something permissions wise that would cause that error? Long shot since it compiles/signs with the 18.104.22.168 SDK fine, but worth asking.
08-17-2012 03:14 PM
at least you have a work around for now.
Can you give me the exact zip you trying to sign? Anyone that fails.
08-17-2012 03:19 PM
I just sent you two, I think I got your email address right..
08-20-2012 04:48 PM
I'm running into the same issue and the posted work around doesn't seem to fix it for me. My PATH variable looks like this:
ryans-macbook-pro:~ rrenna$ echo $PATH /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Appl
ications/Server.app/Contents/ServerRoot/usr/bin:/A pplications/Server.app/Contents/ServerRoot/usr/sbi n:/Developer/SDKs/Research In Motion/BlackBerry 10 WebWorks SDK 22.214.171.124/dependences/tools/bin
But I still get the same error:
[INFO] execvp(): No such file or directory
08-20-2012 05:06 PM
I actually am having problems with it too I just didn't have a chance to follow-up yet. There is another work-around that takes a little more effort. Are you working via the command line?
08-21-2012 09:53 AM - edited 08-21-2012 09:54 AM
This is a weird workaround but it gets it done:
1 - Run BBWP as you normally would, this creates the bar file you need to work with.
2 - Change to the sub directory 'dependencies/tools/bin' and then run ./blackberry-signer -storepass <your password> <location of bar file you just created>
That signs the file properly and allows you to deploy it.
I just checked the issue as well, looks like the problem was and has been fixed for the next release, so hopefully this should be a short term problem
08-21-2012 10:41 AM
The basic problem is that the blackberry-signer is not in your path.
so all you need to do is make sure that the blackberry-signer is added to your path.
export PATH=$PATH:/Developer/SDKs/Research In Motion/BlackBerry 10 WebWorks SDK 126.96.36.199/dependences/tools/bin
So after you apply $PATH workaround above make sure that it actually worked by doing the following-
1. Open a new tab in the terminal
2. just type " which blackberry-signer " (without the quotes)
You should see the location of the blackberry-signer.
If you don't see the location then you know you didn't add the correct path to the dependencies/tools/bin folder.