-
1. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
saumishr Sep 5, 2013 12:14 AM (in response to jefferis)Edge Inspect has nothing to show in the dock. It will only appear on menu bar. Devices and Edge Inspect cc must be on the same wi-fi and you can simply tap on the service name which appeared in your phone. Also to reinstall you can simply: delete the EdgeInspect.app file from Applications (MAC) or use control panel (Win), and can install from Creative Cloud app again.
Can you please verify that port 7682 is open in your PCs firewall for the Edge Inspect application?
-
2. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
jefferis Sep 5, 2013 4:39 AM (in response to saumishr)I have DHCP and NAT enabled on my Mac which is supposed to open ports automatically on the approved network. There is no specific option to open 7682, even though I tried to add that port, it will not let me. My phone and computers are on the same WiFi network (Airport Express), and Edge is not working on either my laptop (connected only by Wifi) or my Desktop (Ethernet to Airport). The iPhone 5 is on the same wireless network.
Edge is showing active in the menu bar in the finder, but when I check the Chrome extension, it does not show it as active, it keeps saying to "start the application."
-
3. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
saumishr Sep 10, 2013 1:33 AM (in response to jefferis)if the Chrome extension icon is gray, that means that either the Edge Inspect desktop application isn't running or the Chrome extension can't talk to it for some reason.
The most likely explanation for your issue is that either some other app is using port 7682 or that port 7682 is blocked. Try closing Chrome and running the netstat check. Make sure some other application is not using the port we need. Try closing all other open apps and then do your check again.
Please run Netstat command to check whether Edge Inspect app is listening on port 7682.
If that doesn't help, could you please follow these steps to help us resolve this issue.
1. Shut down the desktop app.
2. Go to chrome://extensions and check Developer Mode.
3. Then under the Inspect extension, click the "background.html" link next to Inspect Views.
4. Click on the Console tab and start the Edge Inspect desktop app again.
5. Copy and paste whatever appears in the console window into your response here.
-
4. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
danepthomas Sep 10, 2013 3:16 AM (in response to saumishr)I'm also having this issue and it seems these are all related
http://forums.adobe.com/message/5668066
http://forums.adobe.com/message/5045358
http://forums.adobe.com/message/5655668
I've done all the suggested trouble shooting there.
WebSocket connection to 'ws://127.0.0.1:7682/' failed: Error during WebSocket handshake: Sec-WebSocket-Protocol mismatch inspect.js:61
Uncaught SyntaxError: Unexpected token u inspect.js:224
Nothing is blocked on port 7682
Chrome 30.0.1599.28 beta (have tried on Canary)
Latest Edge Inspect CC
As a side note there seems to be some form of connection, if I try to connect from the iPad and it displays the PIN and then I close the app on my desktop the iPad goes back to the connection screen.
Something with the inspect.js file?
-
5. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
jefferis Sep 10, 2013 3:55 AM (in response to saumishr)Netstat does not show anyone trying to use that port.
Here is the Console message in CHrome
Uncaught SyntaxError: Unexpected token u background.html:1Uncaught SyntaxError: Unexpected token u background.html:1
Uncaught SyntaxError: Unexpected token u background.html:1
Uncaught SyntaxError: Unexpected token u background.html:1
Uncaught SyntaxError: Unexpected token u background.html:1
Uncaught SyntaxError: Unexpected token u background.html:1
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- Uncaught SyntaxError: Unexpected token u inspect.js:224
- // this line:
this.receiveError = function (ev) {
var message = JSON.parse(ev.data);
// Pitch the error to the view?
}
-
6. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
sbeattyinsign Sep 14, 2013 3:49 AM (in response to jefferis)I have exactly the same problem. Edge Ispect does work for Edge Code CC and Reflow though, only having problems with Chrome.
Error I get:
WebSocket connection to 'ws://127.0.0.1:7682/' failed: Error during WebSocket handshake: Sec-WebSocket-Protocol mismatch inspect.js:61
Uncaught SyntaxError: Unexpected token u
-
7. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
saumishr Sep 16, 2013 12:09 AM (in response to jefferis)Hi,
We have got some users having the same issue and we are wokring on this. In case we require more help we will send you screen share request.
-
8. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
saumishr Sep 16, 2013 6:02 AM (in response to jefferis)We are seeing some issue of Websocket connection with Chrome Canary beta builds.
Could you all please try the latest stable version of Chrome (v29.0) and let us know if issue persists.
-
9. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
jefferis Sep 16, 2013 6:55 AM (in response to saumishr)It is starting now to work, but weinre is very clunky. It takes several page loads to get it to see the iPhone content on the devices tab. Then in the elements tab you cannot Edit as HTML, which is a drawback. Safari iOS emulator with xcode does not have that problem.
Also, Chrome auto updates to beta versions and I can't find a way of preventing it! Nothing in settings lets me do that, and perhaps turning off developer will, but that interferes with other editing apps.
-
10. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
saumishr Sep 16, 2013 9:18 AM (in response to jefferis)Glad that it helped!
In case you need better performance than you're able to get using the default weinre server, you can run it locally and configure the Edge Inspect extension to use the the local server.
Please follow this doc: http://forums.adobe.com/docs/DOC-2623
Also, As far as I know if you have installed stable Chrome release it only updates to major versions and not to beta. Will check that and let you know.
-
11. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
jefferis Sep 16, 2013 9:20 AM (in response to saumishr)My Chrome was a beta 30 version and I don't remember installing it by choice
-
12. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
cobeyWFI Oct 1, 2013 10:35 PM (in response to saumishr)I'm getting the same error as above:
WebSocket connection to 'ws://127.0.0.1:7682/' failed: Error during WebSocket handshake: Sec-WebSocket-Protocol mismatch
Running Chrome 30.0.1599.66
This is a stable release as far as I can tell. I'm not running Chrome Canary. There is no way to go back to an earlier version as this auto-updates.
Please reply on the state of this fix.
Thanks.
-
13. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
oilpanllc Oct 2, 2013 8:31 AM (in response to jefferis)Chrome auto-update broke my edge inspect. Anybody have instruction/links how to revert to Chrome 29?
-
14. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
sarchetjulie Oct 2, 2013 9:32 AM (in response to oilpanllc)Yes I would like to know how to install Chrome 29 also.....having same problem.
-
16. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
cobeyWFI Oct 2, 2013 7:28 PM (in response to ArnoldD)Yes!!!! Nice find!
Cobey Potter | Wellfire Interactive
cobey.potter@wellfireinteractive.com
(571) 766-6306
@courcelan | @wellfire
-
17. Re: Cannot connect to Mac 10.8.4 with Edge Inspect
saumishr Oct 3, 2013 4:29 AM (in response to jefferis)Hi All,
We are aware of this issue and working actively to resolve it. Will keep you posted about the fix.


