Issue metadata
Sign in to add a comment
|
Chromecast fails to find device when pending Chrome update is downloaded
Reported by
sits...@gmail.com,
Mar 4 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Steps to reproduce the problem: 1. Install Chrome. 2. Use Chromecast button. 3. Wait a few weeks for new Google Chrome update to be downloaded in the background. 4. Try and use Chromecast button. What is the expected behavior? Chromecast to be displayed after a few seconds. What went wrong? Chromecast is never found. Did this work before? N/A Chrome version: 64.0.3282.167 Channel: stable OS Version: OS X 10.12.6 Flash Version: Other devices (e.g. Android phone, iPads) are able to see the Chromecast. Launching another Chrome via an empty profile (e.g. /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=/tmp/chrome/ ) also works.
,
Mar 4 2018
To aid people who are searching the bug tracker, Chrome displays when it can't find the Chromecast is "No Cast Devices Found".
,
Mar 4 2018
,
Mar 4 2018
,
Mar 5 2018
Making this even stranger, going to chrome://cast/#devices in the problem browser finds the device even though View -> Cast does not.
,
Mar 5 2018
It's interesting that an empty profile fixes it for you. Do you mind going into the settings for the missing device from chrome://cast#devices, looking up its IP address, and appending it to the bug? If privacy is a concern I can mark the bug private to Chromium developers.
,
Mar 5 2018
Chromecast information: Firmware version: 1.30.111763 Country Code: GB IP Address: 192.168.0.7 Mac's IP address: 192.168.0.6
,
Mar 5 2018
@mfo... - if you mark the bug as private I will send over the MAC address too.
,
Mar 5 2018
That shouldn't be necessary. Do you mind filing a feedback report by right clicking on the toolbar icon -> Report an Issue? Include this bug #. We'll take a look and see if there is anything we can tell from it.
,
Mar 5 2018
Feedback sent.
,
Mar 6 2018
Hi, just to let you know Chrome has started showing a green arrow to indicate it's time to restart. I'll be restarting this Chrome instance in a day or two so if you need anything more let me know before then as it might be a while before this shows up again.
,
Mar 6 2018
,
Mar 6 2018
I've located the feedback report and we will look at it internally.
,
Mar 6 2018
,
Mar 28 2018
We have been noticed the same issue with Version 64 and 65 of Chrome OS. We have just updated the chromebooks in our school district to version 64 and none of them are able to see any chromecasts when selecting the cast option. We have a tested this across Version 61, 63, 64, and 65. Only on versions 61 and 63 were we able to see any chromecasts under the cast option. If I should create a separate bug or if you need any more info please let me know. I spoke to a google representative who recommended I comment on this issue.
,
Mar 28 2018
Hi gdehoog@, are the Chromecast devices on public IPs? If so, in 64 we started disallowing connecting to Chromecast devices on public IPs due to security reasons. On Chrome 66 or later you can re-enable that feature by passing in --enable-features=CastAllowAllIPs in the command line, or by turning it on in chrome://flags (look for "Connect to Cast devices on all IP addresses"). We are looking to add an enterprise policy for this in Chrome 67.
,
Mar 28 2018
The chromecasts are on public ip addresses. I ran over to one of our classrooms with a private wireless network to test this with a new chromecast and everything works! Thank you so much for the info.
,
Mar 30 2018
,
May 29 2018
The original issue likely has the same root cause as https://bugs.chromium.org/p/chromium/issues/detail?id=835017 and should be fixed by https://chromium.googlesource.com/chromium/src.git/+/86c3f0e1a5237885af245181b12b6f5f181571ef in M68. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sits...@gmail.com
, Mar 4 2018