arabenseifer / google-cast-sdk

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

Debugging via port 9222 does not work anymore #537

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
*What steps will reproduce the problem?*

1. Register an unpublished receiver app
2. Add Chromecast stick to whitelist and waited for at least 15 minutes
3. Make sure to run development and test devices all on the same local network 
without client isolation
4. Start receiver app using a custom Android app
5. Wait until receiver app shows up (works fine, by the way)
6. Try to debug receiver app using Google Chrome browser and the URL 
http://<CAST-IP>:9222

*What is the expected output? What do you see instead?*

I expect to see a minimalistic web page containing the debug session links as 
it used to work just yesterday. Today I always get "This webpage is not 
available", no matter what I am trying to do.

I tried the following steps several times:

- Double/triple/quadruple check the correctness of the IP-address of the cast 
stick. No mistake there, I enter the correct URL into Chrome all the time.

- Rebooted stick several times. That used to fix the problem in the past, but 
since today it doesn't work anymore.

- Removed stick from whitelist in developer console and added it again - waited 
for 15 minutes. Still does not work.

- Restarted wireless router several times. Does not work.

- Performed factory reset on cast stick and reconfigured everything. Does not 
work.

*What version of the product are you using? On what operating system?*

Chromecast firmware version: 27946
Android Mediarouter version: v7:21.0.+
Android Play Services version: 6.5.87
Cast receiver app library version: 2.0.0

*Please provide any additional information below.*

The receiver app is hosted on a local web server that is running on the same 
local network. The receiver app starts just fine and everything is operational. 
I can interact with the receiver app using my Android app, however, debugging 
does not work anymore since today.
The accessibility of the debug port was also very shaky in the past. More often 
that not I got the "Webpage not available" error message, but as other 
developers on Stackoverflow pointed out, rebooting the stick used to fix the 
problem for me so far until today.

Original issue reported on code.google.com by dev.nobu...@gmail.com on 18 Mar 2015 at 8:21

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I could also verify using an nmap port scan that port 9222 is not open while my 
receiver app is running.

Original comment by dev.nobu...@gmail.com on 19 Mar 2015 at 5:28

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
My Chromecast stick is at a point where I can debug my receiver app again after 
rebooting the device. However, every single time the receiver app closes and I 
reopen it, I cannot debug it any more. I have to reboot the stick in order to 
enable port 9222 again.

Original comment by dev.nobu...@gmail.com on 19 Mar 2015 at 7:41

GoogleCodeExporter commented 9 years ago
Can you submit a feedback report and prefix it with "Issue 537"?
https://support.google.com/chromecast/answer/3187017?hl=en

Original comment by jonathan...@google.com on 19 Mar 2015 at 10:23

GoogleCodeExporter commented 9 years ago
Thanks for the response. I used the Chrome browser extension for Chromecast to 
send feedback and attached the Chromecast log.

Original comment by dev.nobu...@gmail.com on 19 Mar 2015 at 10:41

GoogleCodeExporter commented 9 years ago
Thanks, we'll let you know if we need any additional information.

Original comment by jonathan...@google.com on 23 Mar 2015 at 5:40

GoogleCodeExporter commented 9 years ago
I am also experiencing this problem and have submitted feedback as requested by 
Leon Nichols and Ali Nadaff in 
https://plus.google.com/u/0/+JimRenkel2014/posts/P7VQ8jppuKJ?cfem=1

Jim Renkel

Original comment by jim.ren...@gmail.com on 29 Mar 2015 at 11:23