Live Development does not work for a small number of people

[ghost]

I wanted to try out the Live Development on Windows 7 Prof. but it was not working. I was able to launch the Developer tools but the Live Development just stays in 'Connecting...' status.

After lots of Googling and help from @gruehle_ in IRC, we figured out that the Chrome debugger is not getting launched by default. This is the same with both single user Chrome as well as the multi-user Chrome versions.

SOLUTION: Chome has to be specifically started in debug mode to get it working.

cd C:\Program Files (x86)\Google\Chrome\Application
chrome.exe --remote-debugging-port=9222

Filing this bug so that anyone facing this issue can try this solution.

---

More examples of this problem:
http://forums.adobe.com/message/5123185#5123185
http://forums.adobe.com/message/5096983#5096983

[ghost]

OK... I was wondering what was wrong!

[redmunds]

Thanks for posting. This may be related to issue #2154.

[peterflynn]

Simplifying title -- removed "in Sprint 17 experimental public build." @dhanvantaritkv and @noahbuscher, I'm assuming you're still seeing this in newer builds too?

[ghost]

Yes Peter. I am still seeing this in Sprint 18. Haven't tried 19 yet as the newer build of brackets-shell native client is not yet available.

[peterflynn]

@dhanvantaritkv, Sprint 19 is finished so you can download it here: http://download.brackets.io/

[peterflynn]

Also, can you check out NJ's comment in #2154? - #2154 (comment)

Does your project match any of the issues described there? Or more general question would be -- what URL is your project set to? (Did you use the "Project settings" dialog to override the default URL? Are you running a local server at all?)

[ghost]

Hi Peter, sorry for the delay. I tried using build 19 and still see the same problem. The Live development would not launch with out starting the chrome specifically in debug mode. I'm not using any local server and did not set the project settings.
I cant say anything regarding NJ's comments in #2154 as I dont use Node.js. The behavior I see in Live development is that it remains in connecting state and does not connect.

[peterflynn]

Added links to similar reports in the forums, at top.

[njx]

This is in sprint 22 as part of the RESEARCH: Live Development Robustness card. No need to add to the bug card.

[redmunds]

@dhanvantaritkv @noahbuscher A fix for this has been merged into master. You will need an updated version of both brackets and brackets-shell to test this before Sprint 22 is released. Can you build a local version of brackets-shell and test this out?

[redmunds]

Closing.

[artsyrakel]

So, I'm having this problem too. Everything I can find on this has been over a year, so I'm not sure why I'm having this issue. I first installed Edge Code mid last week, and on Friday it started doing this thing where it wanted to relaunch chrome with the remote debugging on. I hit the relaunch button and this error just keeps popping up. This morning I fired up my computer and connected just fine. Great! I thought, it's working! Must have been a fluke. I close it because I wasn't ready to work on anything yet. Well, now I am trying to open it and I'm getting the remote debugging relaunch error again. WTF???

If it helps, it looks like my Chrome is installed in the Program Files directory and not in my individual User folder. I'm also running Windows 7.

[njx]

@artsyrakel It might well be a problem with a recent Chrome update. We've been seeing an increased number of errors in live development in Brackets - some of them are due to Brackets bugs, but it's also possible that timing of various remote debugging events in Chrome has changed lately.

If you're using Chrome beta, you might be running into #6830. Otherwise, you might be running into some of the issues in #5687. Please comment on one of those with what you're seeing. Thanks!

[artsyrakel]

Neither of those issues seem to replicate my issue, whereas the issue in this thread is exactly what's happening. I get this error:

Connecting to Browser

In order for Live Preview to connect, Chrome needs to be relaunched with remote debugging enabled.

Would you like to relaunch Chrome and enable remote debugging?

[ Cancel ] [ Relaunch Chrome ]

If I select Relaunch Chrome, then it closes Chrome and nothing else happens.

I was able to get around this before by uninstalling Chrome and reinstalling it, but that's a pain in the neck to do every time. I did that two days ago, and today it popped up again.

I noticed that since I reinstalled and signed in, it hadn't synced my bookmarks yet, and this morning when I opened it up, my bookmarks were synced. I don't have Adobe Edge Code installed on my computer at home -- perhaps that has something to do with this bug? Maybe it keeps grabbing my settings from my home computer where debugging is not enabled?

[artsyrakel]

OK, so I reinstalled Chrome again, but this time I'm not going to sign in. I'll see if it breaks again. If it doesn't, I'm pretty sure the issue is because of Chrome's syncing capabilities when logged in.

[artsyrakel]

Crap, I am getting this error again! I haven't signed into Chrome this time either. It was working this whole week and now ... :

[njx]

We've made some fixes to the way Live Development connects to the browser in the upcoming release (which should be out in the next few days). Please try it when it comes out, and let us know if you're still seeing issues. Thanks!