Incompatible Chrome Extension? #59

Closed
jacquescrocker opened this Issue Dec 4, 2012 · 9 comments

Projects

None yet

6 participants

@jacquescrocker
Member

I see this error whenever I connect.

error

Is it possible to get this upgraded to the latest version of livereload?

Thanks!

@jacquescrocker
Member

i tried setting the :api_version to 2.3 (and others) but same error every time.

@andreyvit
Member

Hey, guard-livereload is already compatible, and is officially supported by the browser extension (which means that I test the new extension versions for compatibility). It is known to work for other people. Please make sure guard is running (duh), uses the default port and that you have the latest versions of all gems (esp any websocket-related ones; I don't really know which one guard-livereload is using).

Also, don't mess with api_version; it's the legacy protocol and thus the version is fixed at 1.6 forever. (The option can be removed now. If you want to help, send a pull request deleting any mentions of it from the README.)

@jacquescrocker
Member

ok, i'll keep debugging. thanks for the heads up

@jacquescrocker
Member

hmm, seems like the server is running fine, and on the right port

> lsof -iTCP:35729
COMMAND     PID         USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
LiveReloa 58650 ashbhoopathy   12u  IPv4 0x7204a1f1b7c58b45      0t0  TCP *:35729 (LISTEN)
@andreyvit
Member

LiveReload sounds more like the LiveReload app than guard-livereload (which would be listed as something like 'ruby'). Does it happen to run in background? Still does not explain why your extensions cannot connect (perhaps you haven't updated the LiveReload app in a loooong while?)

@jacquescrocker
Member

ah, i think you're probably right. thanks!

@rahilsondhi

I'm having the exact same problem.

Downloaded LiveReload Chrome extension: https://chrome.google.com/webstore/detail/livereload/jnihajbhpnppcggbcgedagnkighmdlei

$ guard -v
Guard version 1.6.2

My Guardfile:

guard 'livereload' do
  watch(%r{.+\.(css|js|html)})
end

Here's what I see when I run guard

guard
23:18:16 - INFO - Guard uses TerminalTitle to send notifications.
23:18:16 - INFO - Guard is now watching at 'MY_DIRECTORY'
23:18:16 - INFO - LiveReload 1.6 is waiting for a browser to connect.
[1] guard(main)>

Guard is indeed running

lsof -iTCP:35729
COMMAND   PID  USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
ruby    53760 rahil    6u  IPv4 0x3af123b68aabfe97      0t0  TCP *:35729 (LISTEN)

If I type exit in my guard console:

[1] guard(main)> exit
23:23:55 - INFO - Browser connected.
23:23:55 - INFO - Browser connected.
23:23:55 - INFO - Browser connected.
23:23:55 - INFO - Browser disconnected.
23:23:55 - INFO - Browser disconnected.
[1] guard(main)> exitwser disconnected.
23:23:55 - INFO - Bye bye...
@thibaudgg
Member

Please ask on support@livereload.com for that kind of issue.

@smerrill

For what it's worth, I had this same issue, and it seems to be related to the pry integration in new guard versions. When I ran guard with guard -i, the problem went away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment