error when chrome cast extension is not installed

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Do not install chrome cast extension or remove it if you have installed.

What is the expected output? What do you see instead?
It should not send ajax request to 
"chrome-extension://boadgeojelhgndaghljhdicfkmllpafd/cast_sender.js" if chrome 
cast extension is not installed.

What version of the product are you using? On what operating system?
Regular chrome and incognito. Mac OSx.

Please provide any additional information below.

I've got the ff errors:

Failed to load resource: net::ERR_ADDRESS_UNREACHABLE 
chrome-extension://boadgeojelhgndaghljhdicfkmllpafd/cast_sender.js
Failed to load resource: net::ERR_ADDRESS_UNREACHABLE 
chrome-extension://dliochdbjfkdbacpmhlcpmleaejidimm/cast_sender.js
Failed to load resource: net::ERR_ADDRESS_UNREACHABLE 
chrome-extension://hfaagokkkhdbgiakmmlclaapfelnkoah/cast_sender.js
Failed to load resource: net::ERR_ADDRESS_UNREACHABLE 
chrome-extension://fmfcbgogabcbclcofgocippekhfcmgfj/cast_sender.js
Failed to load resource: net::ERR_ADDRESS_UNREACHABLE 
chrome-extension://enhhojjnijigcajfphajepfemndkmdlo/cast_sender.js
No cast extension found

Should it not send requests if chrome-extension is not installed?

Original issue reported on code.google.com by oo7...@gmail.com on 30 Jun 2014 at 12:47

[GoogleCodeExporter]

This is per design; in order to know if a user has the Chromecast extension 
installed (and which one), cast_sender.js requests the script from all 
potentially installed extensions.

Original comment by anad...@google.com on 18 Jul 2014 at 5:13

• Changed state: WontFix

[GoogleCodeExporter]

This is terrible coding.

Original comment by 1985....@gmail.com on 13 Sep 2014 at 9:44

[GoogleCodeExporter]

This is amateurish at best, incompetent at worst. It's bad and Chrome 
developers should feel bad. 

Original comment by kathpa...@gmail.com on 15 Sep 2014 at 11:08

[GoogleCodeExporter]

at least keep the console free of errors...

Original comment by gilad.im...@gmail.com on 22 Sep 2014 at 2:32

[GoogleCodeExporter]

Issue 380 has been merged into this issue.

Original comment by riv...@google.com on 22 Sep 2014 at 5:50

[GoogleCodeExporter]

This would be about 3 lines of code to fix. I'm very surprised Chromecast team 
considers it reasonable to dump a long list of error messages in the vast 
majority of people's browsers, ie > 99% of users of a typical web app are 
either using another browser or using Chrome but without Chromecast, and this 
will aversely affect all of them.

"Don’t leave “broken windows” (bad designs, wrong decisions, or poor 
code) unrepaired. Fix each one as soon as it is discovered." [1]. By routinely 
dumping error messages in almost everyone's consoles as if it were a normal 
situation, you are encouraging developers and users to ignore error messages 
instead of taking them seriously, as they should do, and you are making it 
impossible for developers to attain a pristine error log.

1. https://pragprog.com/the-pragmatic-programmer/extracts/software-entropy

Original comment by mich...@mahemoff.com on 22 Sep 2014 at 6:39

[GoogleCodeExporter]

This is ridiculous and very annoying. I dont want to see this error every time 
when developing.

Please fix!

Original comment by jef.kosl...@gmail.com on 22 Sep 2014 at 11:12

[GoogleCodeExporter]

Agree with all comments above. Please fix!

Original comment by Sally.Wo...@gmail.com on 28 Sep 2014 at 5:05

[GoogleCodeExporter]

Very annoying for me too. Trying to fix a bug in a program and it took me a 
while to figure out that this wasn't part of the bug and wasn't something I was 
doing.

Original comment by prof.st...@gmail.com on 29 Sep 2014 at 7:02

[GoogleCodeExporter]

yeah amateurish at best. should fix!

Original comment by rus...@thesearchengineshop.com on 29 Sep 2014 at 7:54

[GoogleCodeExporter]

I have not installed cast sender yet I'm seeing errors in my chrome dev 
console. not good.

Original comment by JonRyanI...@gmail.com on 1 Oct 2014 at 3:39

[GoogleCodeExporter]

Completely ridiculous. It's a simple fix. Fix it.

Original comment by jaysonj...@gmail.com on 1 Oct 2014 at 6:22

[GoogleCodeExporter]

How is this a wontfix? What the heck you guys? Are you expecting patch requests 
for it if someone else tackles it?

Original comment by Meo....@gmail.com on 5 Oct 2014 at 8:22

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I guess we should all leave the Google community and go back to Firefox then...

Original comment by samuelma...@gmail.com on 7 Oct 2014 at 4:21

[GoogleCodeExporter]

Do any of you guys create apps ? e.g. I have created one in the past and 
noticed that within my Eclipse environment, i have downloaded the 'Google Play 
services API' as part of a project. This enables (amongst other things) 'Google 
Cast'. 

Wondering if this could be part of the reason I'm seeing the cast_sender.js 
issues ? or am I clutching at straws....

Original comment by JonRyanI...@gmail.com on 8 Oct 2014 at 3:20

[GoogleCodeExporter]

Jon - that's right, there's no mystery here. I assume Eclipse's "Google Cast" 
will cause your app to link to include the official cast_sender.js script, and 
that script is broken as it insists on trying to fetch a resource that will 
only be present if users are in Chrome and Chromecast extension is installed. 
Otherwise, it will dump errors.

Original comment by mich...@mahemoff.com on 8 Oct 2014 at 5:46

[GoogleCodeExporter]

Annoying!

Original comment by a...@goodfront.com on 15 Oct 2014 at 10:03

[GoogleCodeExporter]

So what, send the requests to detect Chromecast extensions.

*Don't pollute the console.* That's entirely different.

Original comment by TruSktr on 16 Oct 2014 at 4:29

[GoogleCodeExporter]

I think there's something called a try-catch block or something?

Original comment by TruSktr on 16 Oct 2014 at 4:35

[GoogleCodeExporter]

this has been more than 4 months and no one is bothering to reply form the 
development team. It very annoying for me see those error line every time i 
look at the console. Please fix it.

Original comment by buy4me...@gmail.com on 17 Oct 2014 at 4:17

[GoogleCodeExporter]

Is it possible this is affecting Analytics tracking? My Chrome direct traffic 
suddenly dropped on 4th October 2014 without any apparent reason.
Thanks

Original comment by edelcast...@gmail.com on 21 Oct 2014 at 3:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

i'm really puzzled with the attitude towards this issue :/

Original comment by leite.ca...@gmail.com on 22 Oct 2014 at 2:24

[GoogleCodeExporter]

This is a serious issue and interferes with all chrome based web development as 
well as driving developers, like myself, away from using chrome. Please fix 
this ASAP!

Original comment by a...@adamblackerby.com on 23 Oct 2014 at 7:42

[GoogleCodeExporter]

I kinda of understand why it hard to fix, its not chromecast who logging them, 
its chrome browser logging every request failure.

but the thing i don't understand is that, why chrome must check the google 
cast's present even when i don't have it installed?

Original comment by Homyu.Shinn on 24 Oct 2014 at 12:12

[GoogleCodeExporter]

The easy fix, I imagine, is to silence the errors with try catch blocks.

Original comment by TruSktr on 24 Oct 2014 at 10:19

[GoogleCodeExporter]

So it appears that Chrome attempts to get cast_sender.js on pages that have 
YouTube content. I'm guessing when Chrome sees media that it can stream it 
attempts to access the Chromecast extension. When the extension isn't present, 
the error is thrown.

Original comment by l...@lesjames.com on 28 Oct 2014 at 9:06

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Wontfix??? Wtf... Ok, back to Firefox... farewell

Original comment by jaroslav...@gmail.com on 7 Nov 2014 at 10:18

[GoogleCodeExporter]

Why the hell you "wontfix" forgotten debug code "  
console.log(response.farewell);"

Original comment by jaroslav...@gmail.com on 7 Nov 2014 at 10:19

[GoogleCodeExporter]

Its crazy that you wont fix this ! Why ? Really, we, developers love to make 
things properly, so how can we live in peace with this on our console ? Jesus...

Original comment by Avcajara...@gmail.com on 12 Nov 2014 at 9:44

[GoogleCodeExporter]

Wow this is @#$%^&* annoying

Original comment by the.ener...@gmail.com on 12 Nov 2014 at 10:43

[GoogleCodeExporter]

This is causing so much trouble...

Original comment by shair.n...@gmail.com on 13 Nov 2014 at 5:14

[GoogleCodeExporter]

Hey Everyone, we understand that this is annoying, and while this particular 
issue is marked WontFix, we are working on a solution that doesn't depend on 
being able to load content from the extension in this way.

As for the console error, this isn't a simple case of turning off a log 
statement, it's Chrome itself which shows that error on any failed document 
request.  Normally that's fairly useful to have, though we do understand it's 
annoying in this case due to the failed requests for extension resources.  
There's really no way for the Cast JS code to suppress this console output, 
AFAIK.

Original comment by markdavi...@google.com on 13 Nov 2014 at 6:03

[GoogleCodeExporter]

I happened upon this page fearing at first that I had be compromised.  Not a 
pleasant feeling, very thankful that it's a worthless bug.

While this issue is not a show stopper, in fact it looks quite benign, but it 
is still ludicrous that it was marked as WONT FIX.... 

To boot the response on July 18th was less then informative, you guys might 
want to stop and formulate your responses a little more before you post them.  
Especially with 19 days worth of research time between the original post and 
response.

This clean up should happen in the code before a user deals with it, but for 
those wishing to alleviate the issue locally you can filter the output:
http://superuser.com/questions/394213/how-can-i-suppress-chrome-extension-output
-from-web-inspectors-console-log

Filter out all messages from a particular source file by right-clicking the 
white (blank) part of console message line and choosing Filter > Hide Messages 
from foo.js. You can undo this filtering from the same menu later, if you wish. 
Chrome will remember to do this filtering for you until you disable it (even if 
you navigate somewhere else or restart Chrome).

Original comment by jpbh...@gmail.com on 17 Nov 2014 at 6:12

[GoogleCodeExporter]

Uninstalling (not only deactivating )the official google cast extention in 
chrome seems to remove the messages to console. Left google cast (beta) 
installed but deactivated). 

Original comment by morten.s...@gmail.com on 5 Dec 2014 at 9:19

[GoogleCodeExporter]

Actually this error is reportedly preventing youtube to approve a video 
campaign on adwords.. because my video ad is pointing to my site -> which 
contains a youtube video
can anyone help? adwords support is saying that its probably the way i embedded 
the video and it cant be their fault as there are others embedding videos as 
well... ridiculous

Original comment by yan...@didas.co on 5 Dec 2014 at 2:48

[GoogleCodeExporter]

Shame on you Chrome developers for not fixing this yet!

Original comment by gi...@kitchenbug.com on 7 Dec 2014 at 6:59

[GoogleCodeExporter]

What shoulad I say to my clients?
"Please, don't use embeded youtube player"? or 
"Please, don't look at those console red messages - Google has been fixing this 
bug for a half year"? or
"Just change browser"?

Original comment by Palt...@gmail.com on 8 Dec 2014 at 8:12

Attachments:

• cast_sender_js_error.png

[GoogleCodeExporter]

I just discovered this thread after observing these issues in a couple of my 
websites.  Seeing as the status is marked "WontFix", please provide official 
feedback as to how to correctly suppress these errors.  

Thanks.

Original comment by chris.m....@gmail.com on 8 Dec 2014 at 6:53

[GoogleCodeExporter]

This is ridiculous. Please fix this issue. It's annoying as hell.

Original comment by lan...@quve.com on 9 Dec 2014 at 7:09

[GoogleCodeExporter]

Seeing these same errors via a player built today with the IFrame SDK.  
Couldn't  a simple solution be to add a player flag that disables the Cast 
support in the player and the need to make these calls?  Sure that may not help 
to support the product you are selling, but as a  developer who goes through 
the grind to build cleanly performing applications, throwing a bunch of 
"non-error errors" into our consoles is really unforgivable.

Original comment by koo...@gmail.com on 9 Dec 2014 at 8:50

[GoogleCodeExporter]

This has been going on for soooo long. Chrome dev tools are by far the easiest 
and best to work with. You should really fix this soon.

Original comment by dhopki...@gmail.com on 10 Dec 2014 at 11:59

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The longer you sit on the page the more it grows. This is frustrating for 
developers and you guys own most of us because the console is light years 
beyond IE and FF. Now you're gonna mess that up? What's next? You gonna bloat 
the crap out of Chrome like FF did a few years ago?

Original comment by dhopki...@gmail.com on 11 Dec 2014 at 12:15

Attachments:

• chromeErrors.PNG

[GoogleCodeExporter]

Please fix this bug. It's incredibly difficult to develop with this stuff 
constantly polluting my console.

Original comment by ians....@gmail.com on 11 Dec 2014 at 12:25

[GoogleCodeExporter]

Yeah, WTF.. this just started occuring for me as well. It delays page clicks as 
well and I do NOT want to be forced to install a Chromecast extension! This is 
silly

Original comment by info.ced...@gmail.com on 11 Dec 2014 at 7:37

[GoogleCodeExporter]

This cost me half a day to find a solution!! WTF google!

Original comment by cthom...@gmail.com on 11 Dec 2014 at 1:11

[GoogleCodeExporter]

Guys,

Ditto- please address this.

Original comment by timmille...@gmail.com on 11 Dec 2014 at 9:20