search

gfuentesdev / google-cast-sdk

Automatically exported from code.google.com/p/google-cast-sdk
0 stars 0 forks source link

Cast Extension on Windows, API always returns no devices #159

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
1. In windows 7 install either cast extension or cast extension beta
2. Clicking the extension will show the chromecasts on the network correctly, I 
can cast to them from the extension or from inside youtube.
3. My page with chromecast code, when the API initialized the callback always 
returns e as chrome.cast.ReceiverAvailability.UNAVAILABLE

This code works perfectly on mac and on linux. All windows (I've only tested on 
7) machines don't work. I've tested on 2 different networks both wired and 
wireless.

Original issue reported on code.google.com by mor...@gmail.com on 21 Feb 2014 at 6:09

GoogleCodeExporter commented 8 years ago 
Link for Chrome Canary download for those interested:  
https://www.google.com/intl/en/chrome/browser/canary.html

Original comment by tso...@gmail.com on 6 Mar 2014 at 11:03

GoogleCodeExporter commented 8 years ago 
When will this hit Chrome Stable? I'm getting shmammered by 1-star reviews.

Original comment by mathieu....@matbee.com on 7 Mar 2014 at 4:32

GoogleCodeExporter commented 8 years ago 
After upgrading to Canary 35.0.1876.0 on Windows 7 it all works perfectly. 
Thanks for the good bug slaying! Curious to know what the problem was.

Original comment by ClasLePetit on 7 Mar 2014 at 5:51

GoogleCodeExporter commented 8 years ago 
Canary fixes the issue! Good stuff!

Original comment by Jonathan...@gmail.com on 7 Mar 2014 at 7:50

GoogleCodeExporter commented 8 years ago 
I can confirm that Canary (Version 35.0.1877.0 canary) fixed the issue on 
Windows 7. I expect that this will also fix the issue on Linux once deployed; 
currently canary does not appear to be supported on any Linux release. I will 
continue to use the sandbox workaround on Linux until the fix is deployed there.

Thanks for the fast turn around on the fix in Chrome!

Any idea on when the fix will make it into the deployed Chrome on Windows and 
Linux?

Ewald

Original comment by ecand...@gmail.com on 7 Mar 2014 at 11:19

GoogleCodeExporter commented 8 years ago 
The fix has been pushed out; you need to either wait for the update to happen 
or you can go to extension and update it there.

Original comment by anad...@google.com on 8 Mar 2014 at 11:57

GoogleCodeExporter commented 8 years ago 
Its been pushed to Chrome stable?

Original comment by mathieu....@matbee.com on 8 Mar 2014 at 11:58

GoogleCodeExporter commented 8 years ago 
Some confusion here.

1. It's clear that Chrome Canary is updated to fix the issue.
2. Now "wait for the update to happen or you can go to extension and update it 
there"
   makes one believe that updating the extension will also solve the problem.
   (As of now the extension is not updatable, btw)
3. Should an update of the extesnin fix it for the stabel version of Chrome?

Original comment by ClasLePetit on 9 Mar 2014 at 1:36

GoogleCodeExporter commented 8 years ago 
Looks Like the problem is back with Version 35.0.1880.0 canary. It worked for 
me Yesterday 03/08/2014. Today I seem to have the problem again.Can anyone 
please confirm if it is still working.

Original comment by agk4...@gmail.com on 9 Mar 2014 at 10:14

GoogleCodeExporter commented 8 years ago 
I'm having reports that it's back.

Original comment by mathieu....@matbee.com on 9 Mar 2014 at 10:16

GoogleCodeExporter commented 8 years ago 
Yes. Windows 7 latest Chrome Canary. The issue is back, and the bailout of the 
sandbox applies once more.

Original comment by ClasLePetit on 9 Mar 2014 at 11:59

GoogleCodeExporter commented 8 years ago 
Patch was reverted because of introduced crashes. Instability is solved and 
patch is going to be landed soon. It should get into the next canary.
https://code.google.com/p/chromium/issues/detail?id=348692

Original comment by vitalyb...@chromium.org on 10 Mar 2014 at 6:17

GoogleCodeExporter commented 8 years ago 
After upgrade to Chrome "35.0.1883.0 canary" on Windows 7, the device is again 
found, and the cast sender apps via Chrome works without leaving the sandbox.

(The ChromeCast device itself was automatically restarted, so there might have 
been an upgrade as well? I had to do a manual reset though, to get it ready)

Original comment by ClasLePetit on 11 Mar 2014 at 1:25

GoogleCodeExporter commented 8 years ago 
And we're broke again on 35.0.1901.0 canary.

Original comment by clark.je...@gmail.com on 20 Mar 2014 at 7:12

GoogleCodeExporter commented 8 years ago 
re #64 Nothing was changed, could you please collect logs 
(http://www.chromium.org/for-testers/enable-logging) and file a bug at 
http://crbug.com

Original comment by vitalyb...@chromium.org on 20 Mar 2014 at 8:02

GoogleCodeExporter commented 8 years ago 
https://code.google.com/p/chromium/issues/detail?id=354717

Original comment by clark.je...@gmail.com on 21 Mar 2014 at 12:57

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Crhrome 35.0.1901.0 canary on Windows 7, Google Cast (Beta) 14.305.0.0 works as 
in #63. No problems.

Original comment by ClasLePetit on 21 Mar 2014 at 1:49

GoogleCodeExporter commented 8 years ago 
Chrome 34 beta with the Google Cast beta extension has a fix for device 
discovery when using anti-virus software. Please test again and report any 
issues.

Original comment by lnicho...@google.com on 25 Mar 2014 at 7:52

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Chrome 34.0.1847.92 beta-m on Windows 7, Google Cast (Beta) 14.305.0.0 now 
works as it should (equal to Chrome 35.0.1901.0 canary).
Why the reference to anti-virus software? The release version of Chrome doesn't 
work even if anti-virus software is uninstalled.

Original comment by ClasLePetit on 31 Mar 2014 at 11:12

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
The no device problem is back on 
Chrome Version 34.0.1847.116 beta-m on windows 7, Google Cast (Beta) 14.402.0.3.
It still works on Version 36.0.1926.0 canary, Google Cast (Beta) 14.402.0.3

Original comment by ClasLePetit on 5 Apr 2014 at 12:34

GoogleCodeExporter commented 8 years ago 
Pure magic? today it works again...

Original comment by ClasLePetit on 5 Apr 2014 at 9:33

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
This issue was happening for me as well. Chrome Binaries 33.0.1750.152 on 
Gentoo Linux.  I don't have any anti-virus software on this machine.

Some tabs showed the Chromecast, I could "cast this tab" from my sites home 
page.  When I went to a page that had a video to play, using 
DEFAULT_MEDIA_RECEIVER_APP_ID it was failing, no receivers found.  If I tried 
to launch I would also get an error.

My videos were on a different domain (cdn.edoceo.com) than the site hosting the 
players (edoceo.tv).
When I made them all on the same domain, it magically started working again.  
Same tab even, changed the media source to same domain, clicked refresh and 
boom, it's back.  Toggled back to cross-domain video source and the Chromecast 
device disappears from the tab.

Mine might be CORS issue maybe, hope it helps someone else.

Original comment by david.bu...@edoceo.com on 15 Apr 2014 at 4:41

GoogleCodeExporter commented 8 years ago 
As noted above, Chrome 35 (now on beta) has a fix for the specific issue that 
was interfering with mDNS discovery on Chrome under Windows.  There is still an 
occasional issue on Mac that can prevent mDNS discovery, related to the Bonjour 
service, which we're investigating.

However, beyond the Chrome fix, we added a workaround at the extension level; 
we can now support SDK apps even if we find the device only via DIAL and not 
via mDNS.  That should resolve all issues where launch apps like YouTube work, 
but SDK apps do not.  If you see this happening, please let us know.

Note that there are still issues that can interfere with discovery - OS 
settings, firewalls, VPN, proxies, possibly still some AV issues, network 
isolation, etc.  However, these should not disproportionately affect SDK apps.

P.S. matbee folks, really nice app!

Original comment by markdavi...@google.com on 17 Apr 2014 at 6:09

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Oh! amaaaazing news! We're cleaning up the UI so our users don't have to get so 
mad at us when we don't work.

thanks so much! :)

Original comment by mathieu....@matbee.com on 17 Apr 2014 at 6:13

GoogleCodeExporter commented 8 years ago 
Heads up:
A similar bug is happening. Sometimes a chrome://restart fixes the issue but 
I've had multiple reports that receiver unavailable is occurring.

http://www.reddit.com/r/Chromecast/comments/24gugk/some_videostream_tweaks_for_p
eople_experiencing/

Original comment by mathieu....@matbee.com on 1 May 2014 at 9:22

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
OK I THINK I HAVE THE SOLUTION HERE - or well at least this solved the problem 
i was having "receiver list empty" — this applies ONLY to developers working 
with an UN-published app — separate from my code — using the desktop 
Chromecast app i had to change a setting for the Chromecast — I HAD TO MAKE 
SURE THAT THE SERIAL NO WAS BEING SENT TO GOOGLE. 

Once i took this step, the hello world text example started working — 
receiver found

Hope this helps some of you

Original comment by dsruptd....@gmail.com on 17 Jul 2014 at 6:58

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Is your cast device a registered developer device?

Original comment by mathieu....@matbee.com on 5 Mar 2015 at 3:31