Feedback filed using my corp account.

Hey Tommy, did you file general Chrome feedback, or feedback on Cast?  I'm not finding your report in our feedback bucket.

If you're able to repro this again (sounds like you are), can you right-click on the Cast icon in the toolbar and choose to Report an Issue there?  That will make sure we get the proper logs.

I literally had no idea that I had to file feedback for this particular Chrome feature in a totally different way than other Chrome features.

Thanks for the steps for how to file feedback! I'll try to do that next time I'm home!

OK, I'm not making this stuff up, but in my personal profile, I can click "Report an issue", and a new web page for reporting data shows up. However, nothing happens when I do the same thing from my corp profile.

I've tried with and without having the "cast popup" (the popup for casting) open.

Any tips?

I looked into this with nyquist@. The extension was not found in the corp profile, which explained why devices are missing and the feedback page cannot be loaded.

Somehow we got Chrome to download the extension by forcing the load-media-router-component-extension flag to true (even though it should already be true in official Chrome builds?) Though note that the Chrome instance has been upgraded to 60 since the bug report, so it is possible that upgrading Chrome has somehow unstuck things.

Regardless, the problem is still there because the extension listed as disabled in chrome:extensions. The checkbox to enable it is greyed out (presumably due to it beubg a component extension). It does not seem like the extension crashed (due to lack of "extension crashed" bubble nor stack traces in logs). I suggest that we loop in Devlin to troubleshoot why the extension is disabled.

+Devlin, who is the expert on extensions :)

We have a case where the Media Router component extension is disabled, but we do not know why. Are there logs or other things we can look at to figure out the disable reason? Note that the problem seems to be 100% reproducible on nyquist@'s corp profile.

OK, I looked once more and went back to 'Default' and I see the extension as:

* Chrome Media Router - 6017.605.1.4 - [ ] Enabled
I.e. not enabled, and also greyed out.

I think I might have overlooked it the first time. But still, it doesn't seem to help.

@6

For debuggery, go to chrome://prefs-internals and ctrl+f for the extension id.  There should be an entry in extensions.settings that includes a lot of the metadata about the current extension state.  One of them should be disable_reasons.  That's a bitmask of the disable reasons specified in Extension::DisableReason.

That should at least let you know why Chrome thinks the extension is disabled, and there may or may not be other useful information there as well.

Thanks! So, in my case I got:

state: 0 == disabled,
disable_reasons: 1 == disabled by user action
location: 10 == external component extension

I seem to have the following in my chrome://sync-internals -- Sync Node Browser under Extensions:

"SERVER_SPECIFICS": {
  "extension": {
    "disable_reasons": "1",
    "enabled": false,
    "id": "pkedcjkdefgpdelpbcmbmeomcjbeemfm",
    "incognito_enabled": true,
    "installed_by_custodian": false,
    "name": "Cast Device Integration",
    "remote_install": false,
    "update_url": "https://clients2.google.com/service/update2/crx",
    "version": "4916.111.0.1"
  }
},

Sounds like with the fix for  issue 731824  writing the sync data will not be an issue anymore. So blowing away synced data might help (possibly with deleting local data, at least on the first computer that syncs).

Unsure whether  issue 731824  ensures whether we ever read data for unsyncable extensions or not, or whether that was ever an issue.

Tried clearing data from Chrome Sync ( https://chrome.google.com/sync ), which does in fact clear the sync data, but it does not overwrite the local state.

So the fix seems to be both clearing sync data, and then for each and every device that is in this state, throw away the profile data, and sign in again to sync.

Verified solution suggested in comment #12 on the computer this was the main issue on for me, and it worked fine.