You should be able to do everything from node 0.10 again, the 0.11 requirement was removed from coho.
What version of node does BB require? @purplecabbage risingj.com On Thu, May 29, 2014 at 12:07 PM, Martin Gonzalez < martin.c.glez.g...@gmail.com> wrote: > Well I found the problem, it's really strange, but it makes sense. The > problem is the nodist usage ( nodejs version manager for Windows), which is > similar to nvm or n for Mac OS and Linux. > Well the childprocess module, using that application it was failing only > when 'cordova emulate blackberry10', always throwing a error "Error: peer > not authenticated". > It's strange because I tested it nodist with android/wp8 using > create/plugin add/build/emulate and I had no problem with those platforms, > only with cordova emulate blackberry10 it was failing, so that was the > problem. > If anybody else working with blackberry platform it has this kind of > behavior under Windows, it would be better use the regular nodejs > installation instead of nodist. > Tested under Windows 7 and Windows 8. > > > > 2014-05-28 16:16 GMT-05:00 Martin Gonzalez <martin.c.glez.g...@gmail.com>: > > > I have tracked down the problem to the utils.exec, just at the > > childprocess.exec. > > This is the exact command that it's sent in there: > > "c:\Program Files\BlackBerry\BB10 WebWorks SDK 2.0.0.71\cordova-bl > > ackberry\bin\dependencies\bb-tools\bin\blackberry-deploy" -listDeviceInfo > > 192.16 > > 8.153.128 > > > > Note: change for listDeviceInfo at target-utils.js, line 252. just for > > testing porpuses > > the output in here shows a error: > > Error: peer not authenticated > > > > However, the simulator it doesn't have any password, and if I run this > > under a regular cmd, with the webworks in the path, it list the whole > > device information without any problem. The only place where it shows a > > error is when childproces.exec is executed. > > > > Going deeper, I've changed the function on the callback of the > > childprocess to check what's the error, and this is the exact output: > > Error: Command failed: cmd.exe /s /c ""c:\Program Files\BlackBerry\BB10 > > WebWorks SDK > > > 2.0.0.71\cordova-blackberry\bin\dependencies\bb-tools\bin\blackberry-deploy" > > -listDeviceInfo 192.168.153.128" Error: peer not authenticated > > > > Use the same command on a prompt window and it's working just fine. > > It makes no sense. > > > > I have tried with Webworks 1.0, and 2.0 and with the native sdk tools > only > > in the path, same result. > > > > It's pretty a strange situation. > > > > > > > > > > > > > > 2014-05-28 16:05 GMT-05:00 Martin Gonzalez <martin.c.glez.g...@gmail.com > >: > > > > I have rebooted the simulator several times, installed the latest VMWare > >> and the one before of it. > >> It's curious that when I run blackberry-deploy -test <ip> it doesn't > >> return anything. Not a single response, if I use 'blackberry-deploy > >> -listDeviceInfo <ip>' it returns the proper output. > >> > >> > >> > >> 2014-05-28 15:57 GMT-05:00 Bryan Higgins <br...@bryanhiggins.net>: > >> > >> If it is registered in DHCP leases, it should get automatically > detected. > >>> There is a known issue when you upgrade VMWare, the file gets blown > away > >>> and doesn't re-populate until you reboot the simulator. > >>> > >>> What output do you get from 'blackberry-deploy -test <ip>' ? > >>> > >>> You could also try manually registering the target (either by editing > >>> blackberry10.json or running 'target add') and then use 'cordova > emulate > >>> --target'. > >>> > >>> > >>> On Wed, May 28, 2014 at 4:18 PM, Martin Gonzalez < > >>> martin.c.glez.g...@gmail.com> wrote: > >>> > >>> > I've been working with the Blackberry 10 simulator, recently I tried > to > >>> > deploy an app into the simulator but it always fails, even if the > >>> simulator > >>> > is registered at .cordova\blackberry10.json. > >>> > > >>> > steps: > >>> > cordova create BB10Test > >>> > cordova platform add blackberry10 > >>> > cordova build blackberry10 > >>> > > >>> > then > >>> > cordova emulate blackberry10 > >>> > > >>> > Error output: > >>> > C:\Users\Administrator\BB10Test>cordova emulate blackberry10 > >>> > Running command: > >>> > c:\Users\Administrator\BB10Test\platforms\blackberry10\cordova\ > >>> > run.bat --emulator > >>> > Searching for connected BlackBerry 10 Simulator (1/1)... > >>> > No connected BlackBerry 10 emulator found > >>> > Error: > >>> > > >>> > c:\Users\Administrator\BB10Test\platforms\blackberry10\cordova\run.bat: C > >>> > ommand failed with exit code 2 > >>> > at ChildProcess.whenDone > >>> > (C:\Users\Administrator\nodist\bin\node_modules\cor > >>> > dova\node_modules\cordova-lib\src\cordova\superspawn.js:131:23) > >>> > at ChildProcess.EventEmitter.emit (events.js:110:17) > >>> > at maybeClose (child_process.js:992:16) > >>> > at Process.ChildProcess._handle.onexit (child_process.js:1059:5) > >>> > > >>> > C:\Users\Administrator\BB10Test> > >>> > > >>> > The simulator it doesn't have any password, it has activated the > >>> > development mode, it has an ip address registered under the > >>> > vmnetdhcp.leases, and well it's throwing this error, I have checked > my > >>> > environment and using the tools of Webworks 1.0, 2.0 and from the > >>> > Blackberry Native SDK it throws the same error. > >>> > > >>> > Cordova: 3.5.0-0-2.4.0 > >>> > NodeJS(tested with): 10.26, 10.28, 11.12 > >>> > BBTools(tested with): Webworks 1.0, 2.0 and Native SDK > >>> > Simulator(tested with): 10.2.1.1925 & 10.3.0.440 > >>> > OS: Win 7 64 Bit > >>> > > >>> > Is there somebody else facing this problem? > >>> > > >>> > -- > >>> > Regards, > >>> > Martin Gonzalez > >>> > > >>> > >> > >> > >> > >> -- > >> Regards, > >> Martin Gonzalez > >> > > > > > > > > -- > > Regards, > > Martin Gonzalez > > > > > > -- > Regards, > Martin Gonzalez >
