search

hensm / fx_cast

Chromecast Web Sender SDK implementation for Firefox
https://hensm.github.io/fx_cast/
MIT License
1.88k stars 63 forks source link

Netflix blocks fx_cast #297

Closed SupremeBananas closed 5 months ago

SupremeBananas commented 5 months ago

Windows 11 Firefox 125.0.3 (64-bits) 0.3.1 0.3.0

Description If I go on Netflix with fx_cast enabled, Netflix tells me an update is needed (Screenshot) afbeelding

For it to work again I must

  1. disable the extension
  2. refresh the page
  3. log in
  4. re-enable extension
  5. start a series
  6. refresh page again
  7. then cast

Is this a known problem?

hensm commented 5 months ago

Probably the Chrome version in the user agent string is old enough that Netflix no longer support it. You can set a custom user agent in the whitelist settings.

SupremeBananas commented 5 months ago

Probably the Chrome version in the user agent string is old enough that Netflix no longer support it. You can set a custom user agent in the whitelist settings.

I'm not too familiar with that, do I have to specify that below? afbeelding Do I also need to disable the Whitelist, and can I just install the latest version of Chrome and copy the user agent from there? In my case: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36

hensm commented 5 months ago

Yep, that string should be fine, just put it in the user agent field and keep the whitelist enabled.

SupremeBananas commented 5 months ago

That did the trick! Thank you very much!

bric3 commented 4 months ago

Could it be worth, having a notification to update this string, or have an auto-update of the version number ?

It took, me quite a while to figure out this is Netflix screen was due to fx_cast.

hensm commented 4 months ago

@bric3

Yeah, I've considered it before. My issue with that is it'd mean the extension is "phoning home" periodically which I'm not a huge fan of. It's why the versioning scheme for the bridge is based on semver compatibility with the extension, so it can leverage the extension auto-update to notify of bridge updates.

It could be opt-in, but I'm not sure how much benefit that's going to provide since most users aren't going to enable it until after they've gone through the process of troubleshooting it.

Maybe just regular patch version updates with new user agent strings between major/minor versions is the right way to handle this.

bric3 commented 4 months ago

I see your point, maybe something simpler can be done : show a landing page when installing the extension, indicating it needs to report a different User-Agent string for castable websites. And this string is configurable in the extension config. And it is advised to use the same as the latest version of Chrome.