- #GOOGLE CHROMECAST SETUP EXTENSION INSTALL#
- #GOOGLE CHROMECAST SETUP EXTENSION UPDATE#
- #GOOGLE CHROMECAST SETUP EXTENSION CODE#
Current status at top of the post.Want to put your computer’s screen on your TV? You could hook it up with an HDMI cable, but then your computer’s placement depends upon the length of the cable. More whitelist updates have recently been made to clobber these log messages. Thankfully Google's developer relations team are more aware than certain other stakeholders how badly this has affected developer experience.
#GOOGLE CHROMECAST SETUP EXTENSION UPDATE#
Update 4 (April 30): Nope, not yet anyway. Additionally, the team has confirmed the issue no longer affects other browsers as the SDK was updated to only activate if it's in Chrome. Chrome Canary already has the patch, so it should roll out to all users around mid-January. Hopefully some combination of devtools and extensions API will be improved in the future to make it possible to fix this kind of problem without patching the browser.
#GOOGLE CHROMECAST SETUP EXTENSION CODE#
Update 3 : This has finally been fixed! In the end, Chrome team simply added some code to block out this specific error. Public comments on the bug tracker were closed with that update. Update 2 : The team claim there's nothing they can do to remove the error logs as it's a standard Chrome network error and they are still working on a long-term fix. A member of the Chromecast team seems to suggest the issue will be bypassed by a change the team is currently working on.
Update : The problem has now been acknowledged by Google. Configure devtools to hide the error message ( see David's answer below).
#GOOGLE CHROMECAST SETUP EXTENSION INSTALL#
Install the Chromecast extension from here.If you are a user annoyed by these console messages, you can switch to Chrome if not using it already. And I suspect it could be possible to suppress the error even if it is Chrome, but haven't tried anything.) (I believe Chromecast team is not entirely correct as the library could, at the least, avoid requesting the extension scipt if the browser is not Chrome. You can only inform users to ignore the errors. If you are a developer shipping with this library, you can't do anything about it according to Chromecast team. The Chromecast team have indicated they won't fix this bug. Instead of failing silently, it dumps these error messages in all non-Chrome browsers as well as Chrome browsers where the Chromecast extension isn't present. This is a known bug with the official Chromecast JavaScript library. That would suggest we will see this fixed in stable Chrome June-July 2016. Update: After several attempts, it looks like this may have been fixed in latest Chrome builds (per Paul Irish's comment below). Is there a better way to check if Chromecast extension exists? I believe these AJAX requests are a way of asking if Chromecast extension exists. Should this happen or is there a better way to check if Chromecast sender extension exists (not by requesting AJAX request)? Google cast sender is trying to send AJAX requests for local "cast_sender.js". I'm having an error running Chromecast sender in Chrome Incognito or if Chromecast extension is not installed: Failed to load resource: net::ERR_ADDRESS_UNREACHABLE chrome-extension://boadgeojelhgndaghljhdicfkmllpafd/cast_sender.jsįailed to load resource: net::ERR_ADDRESS_UNREACHABLE chrome-extension://dliochdbjfkdbacpmhlcpmleaejidimm/cast_sender.jsįailed to load resource: net::ERR_ADDRESS_UNREACHABLE chrome-extension://hfaagokkkhdbgiakmmlclaapfelnkoah/cast_sender.jsįailed to load resource: net::ERR_ADDRESS_UNREACHABLE chrome-extension://fmfcbgogabcbclcofgocippekhfcmgfj/cast_sender.jsįailed to load resource: net::ERR_ADDRESS_UNREACHABLE chrome-extension://enhhojjnijigcajfphajepfemndkmdlo/cast_sender.js