Error casting tabs

Search This thread

Houndx

Senior Member
Feb 7, 2009
68
14
I've rooted, installed Eureka and everything has been peachy until tonight. Now I'm able to cast YouTube from my tablet and from the player in Chrome but if I try to cast a tab then the Chromecast shows "404 cannot find the requested version of the receiver app." Something something try again later, update the browser's CV extension. I've been able to cast tabs before tonight without issue. Searching was fruitless. Chrome and the cast extension are up to date. Rebooting the desktop and chromecast did not help either.

Any help in resolving this would be greatly appreciated.
 

Kyonz

Senior Member
Jun 7, 2010
191
273
Auckland, New Zealand
Sorry to hear this, I'll check my own now and do some troubleshooting!

Get back to you shortly with the results of my tests.

---------- Post added at 09:55 PM ---------- Previous post was at 09:24 PM ----------

Hi All,

Just did some checking and this appears to be a problem based on some changes from Google.

As of the latest updates to the Chrome plugin for chromecast it is no longer trusted against the older receiver (that we use for fling support). This is greatly unfortunate and we'll look to a solution as soon as possible.

In the mean time you can regain this functionality by changing your whitelist provider to google and restarting (however will lose fling and all the other nice goodies), we'll look at getting this fixed as soon as we can.

Kind regards,
Kyonz

---------- Post added at 10:13 PM ---------- Previous post was at 09:55 PM ----------

Hi All,

I managed to force the receiver version so it believes it's being sent from the old receiver and thus loads correctly.

This appears to be working (have tested via both tab casting and fling) and is now pushed out to the Team Eureka whitelist (you can reboot to force your device to update or it will receiver it within the next 24hours).

Sorry about this bug being experienced and thanks for bringing it to my attention via this thread. If you have any issues please let me know.

Kind regards,
Kyonz
 

loceys

New member
Feb 9, 2014
2
0
Error Casting

Sorry to hear this, I'll check my own now and do some troubleshooting!

Get back to you shortly with the results of my tests.

---------- Post added at 09:55 PM ---------- Previous post was at 09:24 PM ----------

Hi All,

Just did some checking and this appears to be a problem based on some changes from Google.

As of the latest updates to the Chrome plugin for chromecast it is no longer trusted against the older receiver (that we use for fling support). This is greatly unfortunate and we'll look to a solution as soon as possible.

In the mean time you can regain this functionality by changing your whitelist provider to google and restarting (however will lose fling and all the other nice goodies), we'll look at getting this fixed as soon as we can.

Kind regards,
Kyonz

---------- Post added at 10:13 PM ---------- Previous post was at 09:55 PM ----------

Hi All,

I managed to force the receiver version so it believes it's being sent from the old receiver and thus loads correctly.

This appears to be working (have tested via both tab casting and fling) and is now pushed out to the Team Eureka whitelist (you can reboot to force your device to update or it will receiver it within the next 24hours).

Sorry about this bug being experienced and thanks for bringing it to my attention via this thread. If you have any issues please let me know.

Kind regards,
Kyonz


I rebooted the chromecast multiple times and it says that it updates through Eureka but when it's all done I keep getting the message "404 - Not Found cannot load the requested version of the CV receiver app. Please try again later. If the problem persists, try updating the CV extension in your browser".
 

Asphyx

Senior Member
Dec 19, 2007
2,158
378
Android Wear
Google Pixel Watch
Just did some checking and this appears to be a problem based on some changes from Google.

As of the latest updates to the Chrome plugin for chromecast it is no longer trusted against the older receiver (that we use for fling support). This is greatly unfortunate and we'll look to a solution as soon as possible.

With the public release of the SDK the receiver went from V1 to V2.
Both should still work (because Plex is still using the old receiver if I'm not mistaken) but there may be something different in the way it gets called such as doing a check on the Whitelist for which receiver is required?
 
  • Like
Reactions: loceys

r00t4rd3d

Senior Member
A few things to try:

Make sure you network is set to Home Network not private or public.

Make sure you disable any virtual network cards like what Virtual Box installs.

If on Windows 8 , right click on your wireless network and make sure Sharing is turned ON.

Windows 8.1 Change PC Settings, Network, pick your network, Find devices and content is set to ON.
 
  • Like
Reactions: loceys

loceys

New member
Feb 9, 2014
2
0
A few things to try:

Make sure you network is set to Home Network not private or public.

Make sure you disable any virtual network cards like what Virtual Box installs.

If on Windows 8 , right click on your wireless network and make sure Sharing is turned ON.

Windows 8.1 Change PC Settings, Network, pick your network, Find devices and content is set to ON.

Well, I tried casting today and without rhyme or reason it started working so, thanks for the suggestions.
Also, I wanted to know can I cast TWC via Chromecast browser because I get the message "contents on this page is not supported"
 
Last edited:

Asphyx

Senior Member
Dec 19, 2007
2,158
378
Android Wear
Google Pixel Watch
Well, I tried casting today and without rhyme or reason it started working so, thanks for the suggestions.
Also, I wanted to know can I cast TWC via Chromecast browser because I get the message "contents on this page is not supported"

I suspect it was always a Google Backend problem...
How to implement V2 of the receiver while trying not to break those who still used V1 or had not updated to the new GServices yet.
They didn't succeed at first try I bet! LOL
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Sorry to hear this, I'll check my own now and do some troubleshooting!

    Get back to you shortly with the results of my tests.

    ---------- Post added at 09:55 PM ---------- Previous post was at 09:24 PM ----------

    Hi All,

    Just did some checking and this appears to be a problem based on some changes from Google.

    As of the latest updates to the Chrome plugin for chromecast it is no longer trusted against the older receiver (that we use for fling support). This is greatly unfortunate and we'll look to a solution as soon as possible.

    In the mean time you can regain this functionality by changing your whitelist provider to google and restarting (however will lose fling and all the other nice goodies), we'll look at getting this fixed as soon as we can.

    Kind regards,
    Kyonz

    ---------- Post added at 10:13 PM ---------- Previous post was at 09:55 PM ----------

    Hi All,

    I managed to force the receiver version so it believes it's being sent from the old receiver and thus loads correctly.

    This appears to be working (have tested via both tab casting and fling) and is now pushed out to the Team Eureka whitelist (you can reboot to force your device to update or it will receiver it within the next 24hours).

    Sorry about this bug being experienced and thanks for bringing it to my attention via this thread. If you have any issues please let me know.

    Kind regards,
    Kyonz
    1
    Just did some checking and this appears to be a problem based on some changes from Google.

    As of the latest updates to the Chrome plugin for chromecast it is no longer trusted against the older receiver (that we use for fling support). This is greatly unfortunate and we'll look to a solution as soon as possible.

    With the public release of the SDK the receiver went from V1 to V2.
    Both should still work (because Plex is still using the old receiver if I'm not mistaken) but there may be something different in the way it gets called such as doing a check on the Whitelist for which receiver is required?
    1
    A few things to try:

    Make sure you network is set to Home Network not private or public.

    Make sure you disable any virtual network cards like what Virtual Box installs.

    If on Windows 8 , right click on your wireless network and make sure Sharing is turned ON.

    Windows 8.1 Change PC Settings, Network, pick your network, Find devices and content is set to ON.