search

waasilzamri / chrometophone

Automatically exported from code.google.com/p/chrometophone
0 stars 0 forks source link

Port error: Could not establish connection. Receiving end does not exist. miscellaneous_bindings:232 #451

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Please answer the questions about build version and network, will save
developers a lot of time !

What steps will reproduce the problem?
1. Install and enable Chrome to Phone Extension
2. Open the JavaScript console in the developer tools on Chrome (Desktop)
3. Load any page

What is the expected output? What do you see instead?
Expected output is not to see an error. Instead, an error is seen:
Port error: Could not establish connection. Receiving end does not exist. 
miscellaneous_bindings:232

Please provide any additional information below.
Using Google Chrome Version 20.0.1132.47 on Mac OS X 10.7.4 Build 11E53

Original issue reported on code.google.com by paulyoun...@gmail.com on 2 Jul 2012 at 2:49

GoogleCodeExporter commented 9 years ago 
I'm getting the same error in chrome 20.0.1132.47 on Max OS X 10.6.8.
I confirmed by disabling and each plugin one by one and this was the culprit.

Original comment by william.kral on 3 Jul 2012 at 11:45

GoogleCodeExporter commented 9 years ago 
I can confirm the same error in Chrome 20.0.1132.47 on Windows 7 x64.  I 
confirmed in the same way as william.kral

Original comment by hutch...@gmail.com on 5 Jul 2012 at 2:41

GoogleCodeExporter commented 9 years ago 
the same error and version. it begun after I've updated my chrome!

Original comment by calebeb...@gmail.com on 5 Jul 2012 at 7:39

GoogleCodeExporter commented 9 years ago 
I can confirm as well in Chrome 20.0.1132.47 on Windows 7 x64 with Chrome to 
Phone extension.

Original comment by dustin.g...@gmail.com on 6 Jul 2012 at 3:19

GoogleCodeExporter commented 9 years ago 
I believe this is the extension trying to connect to the Port when the tab is 
not yet ready i.e the status is still "loading" instead of "complete"

This used to work on previous versions but no longer works now. 

At least, that was the issue we had with our extension

Original comment by hassenbe...@gmail.com on 7 Jul 2012 at 3:00

GoogleCodeExporter commented 9 years ago 
I have the same problem with my extension.
It happens after I moved to manifest version 2 and replaced the 
"background_page" with "background.scripts"

Original comment by piotr...@gmail.com on 9 Jul 2012 at 11:52

GoogleCodeExporter commented 9 years ago 
Confirmed in 20.0.1132.47

Original comment by askrenes@gmail.com on 9 Jul 2012 at 2:40

GoogleCodeExporter commented 9 years ago 
confirmed 20.0.1132.47 m

Original comment by mathew.k...@gmail.com on 9 Jul 2012 at 6:29

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Confirmed in 20.0.1132.57

A possible solution may be at: 
http://stackoverflow.com/questions/9106519/port-error-could-not-establish-connec
tion-receiving-end-does-not-exist-in-chr

Original comment by jro...@gmail.com on 13 Jul 2012 at 2:16

GoogleCodeExporter commented 9 years ago 
Any update on this???  Getting same error in 20.0.1132.57 m

Original comment by mattgpar...@gmail.com on 14 Jul 2012 at 10:59

GoogleCodeExporter commented 9 years ago 
Please, consider my solution at http://stackoverflow.com/a/11566747/1346510 
(tested working in 20.0.1132.57 m on Windows 7).

Original comment by babak.j...@gmail.com on 19 Jul 2012 at 6:08

GoogleCodeExporter commented 9 years ago 
Duplicate of http://code.google.com/p/chrometophone/issues/detail?id=316

Original comment by HealthyE...@gmail.com on 28 Jul 2012 at 1:45

GoogleCodeExporter commented 9 years ago 
for me Google Dictionary (by Google) plugin was the culprit. Disabling it 
resolved the issue

Original comment by m.zahida...@gmail.com on 31 Jul 2012 at 7:23

GoogleCodeExporter commented 9 years ago 
Windows 7 x64 dev environment here, chrome 21 

It's definitely a bug with Chrome to Phone. I have both dictionary and chrome 
to phone installed and upon deactivation of dictionary it still showed. I then 
re-enabled dictionary and disabled Chrome to Phone and the port error went 
away. I tried multiple variations of disabling, uninstalling, etc and my 
findings seem consistent.

Original comment by Christop...@gmail.com on 3 Aug 2012 at 5:53

GoogleCodeExporter commented 9 years ago 
for me 'Chrome To Phone' Extension caused the error, when disabling the 
extension the error disappeared.

Original comment by zdeb...@gmail.com on 10 Aug 2012 at 6:58

GoogleCodeExporter commented 9 years ago 
Same here, disabling 'Chrome To Phone' and the error is gone.

Original comment by luisflo...@gmail.com on 10 Aug 2012 at 5:59

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I have confirmed this as well. Running 21.0.1180.79.

Original comment by mynameis...@gmail.com on 15 Aug 2012 at 9:45

GoogleCodeExporter commented 9 years ago 
Bump... noticed this Mac OSX running Version 21.0.1180.82 chrome...

Come on guys get it fixed! will be using FireFox at this rate..

Original comment by ad...@xws.im on 24 Aug 2012 at 7:25

GoogleCodeExporter commented 9 years ago 
same here with Chrome 21.0.1180.89 and  Chrome to Phone Extension 2.3.1

Original comment by j...@graavy.com on 5 Sep 2012 at 3:28

GoogleCodeExporter commented 9 years ago 
Chrome 21.0.1180.89 on Mac OS X 10.7.4

Original comment by janiis...@gmail.com on 13 Sep 2012 at 7:06

GoogleCodeExporter commented 9 years ago 
Same for me : 21.0.1180.89 m on Windows 7 64.
The "Chrome to mobile" fixed the issue for some users but it seems it's for 
Android 4 with chrome only.

Original comment by berth...@gmail.com on 19 Sep 2012 at 8:45

GoogleCodeExporter commented 9 years ago 
had same error message on Ubuntu 12.04.1 and Chrome Version 21.0.1180.89 and I 
do have Chrome2Phone installed

Original comment by son.c...@gmail.com on 28 Sep 2012 at 3:42

GoogleCodeExporter commented 9 years ago 
Original:
issue 316

Duplicates:
issue 451
issue 452
issue 456

64 total votes at time of comment.

Original comment by gic...@gmail.com on 2 Oct 2012 at 6:49

GoogleCodeExporter commented 9 years ago 
Chrome23.0.1271.40 beta-m on Seven
Same problem

Original comment by molokoloco on 19 Oct 2012 at 9:39

GoogleCodeExporter commented 9 years ago 
Same issue Chrome 22.0.1229.94, win 7 64

Original comment by riotr...@gmail.com on 22 Oct 2012 at 1:26

GoogleCodeExporter commented 9 years ago 
Same issue Chrome 23.0.1271.64 m, win 7 64

Original comment by cainrus on 11 Nov 2012 at 5:25

GoogleCodeExporter commented 9 years ago 
same problem. Chrome 23.0.1271.64 m, win7@64

Original comment by reje...@gmail.com on 12 Nov 2012 at 3:27

GoogleCodeExporter commented 9 years ago 
same problem for me too. Version 24.0.1312.14 beta-m

Original comment by Flappe...@gmail.com on 19 Nov 2012 at 10:09

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
 Same here. 23.0.1271.64 m, Windows 7 Ultimate 64 bit

Original comment by kont...@julianclaus.de on 19 Nov 2012 at 5:39

GoogleCodeExporter commented 9 years ago 
confirmed. This needs to be updated.

Original comment by astef...@gmail.com on 21 Nov 2012 at 7:53

GoogleCodeExporter commented 9 years ago 
I have the same issue 23.0.1271.64 on W7 x64

Disabling the extension removes the error in the console.

Please fix Google!

Original comment by m...@purplepixelmedia.co.uk on 27 Nov 2012 at 6:52

GoogleCodeExporter commented 9 years ago 
Same in Chrome 23.0.1271.97 m, Chrome to Phone 2.3.1.

Original comment by i8b...@gmail.com on 3 Jan 2013 at 5:40

GoogleCodeExporter commented 9 years ago 
Chrome version 24.0.1312.57 m
Chrome to Phone version 2.3.1

Original comment by Brian.Ge...@gmail.com on 11 Feb 2013 at 4:58

GoogleCodeExporter commented 9 years ago 
for me it was "followScout" extension issue. once uninstalled got rid of that 
error message.

Original comment by aash...@gmail.com on 18 Feb 2013 at 10:47

GoogleCodeExporter commented 9 years ago 

Still in 2.3.1 on Ubuntu as of today. I'm a big fan of this extention but this 
issue is 10 months old - is anyone maintaining the code?

Original comment by cholte...@gmail.com on 10 Apr 2013 at 4:07

GoogleCodeExporter commented 9 years ago 
had to uninstall "Chrome to Phone" to get rid of error msg.

Original comment by djams...@gmail.com on 17 Jun 2013 at 7:37

GoogleCodeExporter commented 9 years ago 
somehow it's AdBlock on my end and it's messing my Cookie upon signing up. I'm 
using Version 27.0.1453.116 m

Original comment by loreto.g...@gmail.com on 1 Jul 2013 at 4:21

GoogleCodeExporter commented 9 years ago 
Got this error as well.  
Chrome to Phone version 2.3.1.
Chrome version 28.0.1500.71

Original comment by likeach...@gmail.com on 15 Jul 2013 at 2:38

GoogleCodeExporter commented 9 years ago 
Confirmed on Chrome to Phone Extension 2.3.2, Chrome 29.0.1547.66 m.  Running 
Windows 7  Ultimate SP1.

Original comment by nguyen....@gmail.com on 4 Sep 2013 at 2:52

GoogleCodeExporter commented 9 years ago 
same error Chrome Version 29.0.1547.66 m
Port: Could not establish connection. Receiving end does not exist. [VM] 
lastError (24):29
Port: Could not establish connection. Receiving end does not exist. [VM] 
lastError (24):29
Port: Could not establish connection. Receiving end does not exist.

Original comment by isagee...@gmail.com on 17 Sep 2013 at 11:16

GoogleCodeExporter commented 9 years ago 
Had trouble with facebook! I edited my "personal filters" within adblock 
(DELETE!) and whooosh 'tis back :) .... maybe some trouble in a blocked [DIV] 
or something else :)

Original comment by i6813...@gmail.com on 26 Dec 2013 at 8:52