console.log: valence: PowerShell -Command ps ios-webkit-debug-proxy: Terminated with error code: 4294901760

[elennaro]

Firefox nightly, ios-webkit-debug-proxy-win32 v 2014-02-14 windows 8.1

1. got valence and run it as in instruction jpm run -v -b /c/Program\ Files/Firefox\ Nightly/firefox.exe

2. entered WebIDE run Safari/Firefox and other webview on ide

   got log:

Shumway is registered
console.error: valence:
  PowerShell -Command ps ios-webkit-debug-proxy: I
console.log: valence: PowerShell -Command ps ios-webkit-debug-proxy: Terminated with error code: 4294901760
console.log: valence: Connecting to http://localhost:9230
console.log: Connection status changed: connecting
console.log: Connection status changed: connected

Then nothing happens.

[past]

What do you get if you go to the valence tools/win32 subdirectory and run the proxy from powershell like this:

ios-webkit-debug-proxy.exe -c null:9221,:9230-9240 --no-frontend

[past]

Also try it from cmd.exe instead of powershell and see if there are any differences.

[elennaro]

Thank you for your hint @past .
I've did exactly as you told me.
Unfortunately no luck.
After installing Valence (I don't actually thing this is about Valence, just a coincidence I hope) I'm also experiencing some problems with ios-webkit-debug-proxy-win32 itself. it seems it stopped working standalone :(
So I will deal with ios-webkit-debug-proxy-win32 first. And then retry with Valence.

[elennaro]

So the issue I mentioned is resolved. ios-webkit-debug-proxy-win32 works fine with Chrome.

While testing Valence I've mentioned a few things:

1) It starts ios-webkit-debug-proxy-win32 itself and see the log below.

console.error: valence:
  PowerShell -Command ps ios-webkit-debug-proxy: I
console.log: valence: PowerShell -Command ps ios-webkit-debug-proxy: Terminated with error code: 4294901760
console.log: valence: Connecting to http://localhost:9230
console.log: Connection status changed: connecting
console.log: Connection status changed: connected

However no debug console appears in WebIDE.

2) When I close Valence with Ctrl+C the ios-webkit-debug-proxy process stays unkilled.

[artygus]

@elennaro it can be the issue with _rpc_applicationUpdated message, please try to replace tools/win32/ios-webkit-debug-proxy.exe with the patched executable

@past btw i updated the latest binaries on sourceforge

[past]

Thanks @artygus, I've merged your changes in PR #157. @elennaro can you test the ios-win-applicationUpdated branch from my fork to see if it works now for you?

[elennaro]

@artygus @past thank you.
I seem to be weak in this topic so I describe exactly what I do, step by step.

I have Firefox Nightly installed at "C:\Program Files\Firefox Nightly", Web Inspector turned on in mobile safari settings, phone connected to USB.

And from cmd in admin mode i do:,

1. In D:\Valence\ i do git clone -b ios-win-applicationUpdated https://github.com/past/valence.git && cd valence
2. D:\System\Valence\valence> npm install -g jpm
3. D:\System\Valence\valence> npm install
4. D:\System\Valence\valence> jpm run -v -b "c:\Program Files\Firefox Nightly\firefox.exe"
5. In appeared Firefox Nightly I choose WebIDE and Select Runtime: "Safari/Firefox and other webviews"
6. If Firewall is on (I tried both ways): Firewall notification appears where I agree to let ios-webkit-proxy-win32 to do whatever it neads
7. Nothing changes in WebIDE and the Valence log says:

console.error: valence:
  PowerShell -Command ps ios-webkit-debug-proxy: I
console.log: valence: PowerShell -Command ps ios-webkit-debug-proxy: Terminated with error code: 4294901760
console.log: valence: Connecting to http://localhost:9230
console.log: Connection status changed: connecting
console.log: Connection status changed: connected

[past]

Did you check the application list on the left? Have you read the docs before?

[elennaro]

@past I did read the docs, sure.
There was nothing in the list untill I've killed previous ios-webkit-debug-proxy process, that was last from yesterday's test.
So after the rpc update everything woked.
And for last test everything worked.
Just some old unkilled ios-webkit-debug-proxy was making problems.
Thanks a million times for your help!
So should I close?

[past]

Ah, an old proxy process could explain these symptoms. Thanks for filing, I'll close the issue after I merge the fix.

[past]

Closed via 4b99ed8.