Custom receiver - Connection timeout error 15

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a custom receiver with nothing inside the HTML body and using the 
provided sample JS.
2. Use the provided sample Android sender code.
3. Serve the receiver app either locally on the same Wi-Fi network, or on a VPS.
4. Connect the sender app.

What is the expected output? What do you see instead?
The connection should stay connected indefinitely; or at least a long period of 
time. It instead disconnects after exactly 21 seconds since onConnected() is 
called, each time.

What version of the product are you using? On what operating system?
Android 5.1 with latest SDK on sender end. Probably latest SDK on receiver as 
well. Chromecast FW version 27946.

Please provide any additional information below.

Sender logs:

04-18 23:06:48.373  29127-29127/com.app.debug D/MainActivity﹕ 
ApplicationConnectionResultCallback.onResult: statusCode15
04-18 23:06:48.373  29127-29127/com.app.debug E/MainActivity﹕ application 
could not launch
04-18 23:06:48.373  29127-29127/com.app.debug D/MainActivity﹕ teardown

Receiver logs:

Failed to load resource: the server responded with a status of 404 (Not Found)  
 - an image url
cast.receiver.logger.setLevelValue(cast.receiver.LoggerLevel.DEBUG);  - changed 
the debug level
'HTMLHeadElement.profile' is deprecated. The reflected attribute has no effect. 
 -  (program):3
[ 27.075s] [cast.receiver.CastReceiverManager] Version: 2.0.0.0025
cast_receiver.js:13 [ 27.177s] [goog.net.WebSocket] Opening the WebSocket on 
ws://localhost:8008/v2/ipc   - cast_receiver.js:13
undefined
[ 28.360s] [goog.net.WebSocket] WebSocket opened on ws://localhost:8008/v2/ipc  
- cast_receiver.js:13 
[ 28.368s] [cast.receiver.IpcChannel] IpcChannel opened  - cast_receiver.js:13
[ 28.378s] [cast.receiver.CastMessageBus] Dispatching CastMessageBus message  - 
cast_receiver.js:13
[ 28.391s] [cast.receiver.CastReceiverManager] Underlying message bus is open  
- cast_receiver.js:13
[ 28.398s] [cast.receiver.IpcChannel] IPC message sent: 
{"namespace":"urn:x-cast:com.google.cast.system","senderId":"SystemSender","data
":"{\"type\":\"ready\",\"statusText\":\"Ready to 
cast\",\"activeNamespaces\":[\"urn:x-cast:com.domain.app.debug\"],\"version\":\"
2.0.0\",\"messagesVersion\":\"1.0\"}"}  - cast_receiver.js:13
[ 28.415s] [cast.receiver.IpcChannel] IPC message sent: 
{"namespace":"urn:x-cast:com.google.cast.system","senderId":"SystemSender","data
":"{\"type\":\"startheartbeat\",\"maxInactivity\":6000}"}  - cast_receiver.js:13
[ 28.448s] [cast.receiver.IpcChannel] Received message: 
{"data":"{\"applicationId\":\"259E81C4\",\"applicationName\":\"Name\",\"deviceCa
pabilities\":\"{\\\"display_supported\\\":true}\",\"launchingSenderId\":\"1715:c
om.domain.app.debug-85\",\"messagesVersion\":\"1.0\",\"sessionId\":\"E41CEBAC-D9
38-479E-B278-A468F33EC597\",\"type\":\"ready\",\"version\":\"1.12.27946\"}","nam
espace":"urn:x-cast:com.google.cast.system","senderId":"SystemSender"}  - 
cast_receiver.js:13
[ 28.462s] [cast.receiver.CastMessageBus] Dispatching CastMessageBus message  - 
cast_receiver.js:13
[ 28.483s] [cast.receiver.CastReceiverManager] Dispatching CastReceiverManager 
system ready event  - cast_receiver.js:13
Received Ready event: 
{"id":"259E81C4","name":"Name","sessionId":"E41CEBAC-D938-479E-B278-A468F33EC597
","namespaces":["urn:x-cast:com.domain.app.debug"],"launchingSenderId":"1715:com
.domain.app.debug-85"}  - javascript.js:13
[ 28.509s] [cast.receiver.IpcChannel] IPC message sent: 
{"namespace":"urn:x-cast:com.google.cast.system","senderId":"SystemSender","data
":"{\"type\":\"setappstate\",\"statusText\":\"Application status is 
ready...\"}"}   - cast_receiver.js:13
Modernizr 2.0.6 detected. This version is known to cause issues with async 
JavaScript loaders. Please upgrade to at least 2.6: http://modernizr.com/  - 
rocket.js:4
[ 59.433s] [cast.receiver.CastReceiverManager] Dispatching shutdown event    - 
cast_receiver.js:13

Original issue reported on code.google.com by bogdan.z...@gmail.com on 18 Apr 2015 at 8:23

[GoogleCodeExporter]

Also worth noting, the initial StackOverflow threads:
http://stackoverflow.com/questions/29558778/cast-connection-timeout
http://stackoverflow.com/questions/29621040/custom-receiver-connection-failed

Also wanted to point out the fact that Twitch had issues in the past similar 
with this one. The user would cast the Twitch stream over to Chromecast, the 
video would play for 5-10 seconds, only to be disconnected immediately.

Original comment by bogdan.z...@gmail.com on 18 Apr 2015 at 8:27

[GoogleCodeExporter]

Original comment by na...@google.com on 20 Apr 2015 at 10:54

• Changed state: Acknowledged

[GoogleCodeExporter]

Please send a feedback report and prefix it as "for Issue 567". 

Original comment by na...@google.com on 20 Apr 2015 at 11:54

[GoogleCodeExporter]

The app ID: 259E81C4 is invalid. Has the app been published yet? 

Original comment by na...@google.com on 22 Apr 2015 at 5:45

• Changed state: NeedInfo

[GoogleCodeExporter]

No, it's in testing mode. It should still obviously work, otherwise how the 
hell can we test if our implementation is in good shape or not?

Original comment by bogdan.z...@gmail.com on 23 Apr 2015 at 4:53

[GoogleCodeExporter]

Thank you for the information. We are investigating the issue, will update the 
issue accordingly. 

Original comment by na...@google.com on 23 Apr 2015 at 6:53

• Changed state: Acknowledged

[GoogleCodeExporter]

Receiver did not send response because the app is not published. 

Please feel free to respond if you face the issue even after publishing your 
app and we would reopen the ticket. 

Original comment by na...@google.com on 13 May 2015 at 6:12

• Changed state: Invalid

[GoogleCodeExporter]

The problem described in the stackoverflow thread on
http://stackoverflow.com/questions/29621040/custom-receiver-connection-failed

is occurring on a published app, so that's not the issue.

Original comment by Neferetheka@gmail.com on 13 May 2015 at 6:27

[GoogleCodeExporter]

Since the information provided are for an unpublished app, we have concluded as 
such. If you are seeing the issue as described in the StackOverflow question, 
please provide all the relevant information which will help us repro the issue 
and we will gladly reopen the ticket.  

Original comment by na...@google.com on 13 May 2015 at 6:44

[GoogleCodeExporter]

I'm the author of the SO thread.
My application is Astonishing Comic Reader, app id: B0BDC472 It's published. 
I've the same logs as described before, using the sample Android app and the 
sample receiver.

Original comment by Neferetheka@gmail.com on 13 May 2015 at 6:55

[GoogleCodeExporter]

I can't believe I'm actually reading this... We can't test the app we're 
building, because it keeps getting disconnected and you're telling me this is 
caused by the fact that the app is not published yet? How are we supposed to 
publish the app if we are still building it? Publish it, just so that we can 
test it? You do realize how idiotic that sounds, right? No pun intended, but 
I'm completely astonished by your response. Didn't expect this system 
implementation from Google engineers... 

Do you guys release the Cast SDK incomplete just so that you can test it, or do 
you test it fully and release it after you've finished building it? If you're 
taking the same approach as your answer, this explains the whole problem...

I expect a solution to this matter, as your current response is purely 
unacceptable.

Original comment by bogdan.z...@gmail.com on 14 May 2015 at 3:12

[GoogleCodeExporter]

After updating chromecast my application is not running. Android sender launch 
application. Application run, but in callback timeout. Application and custom 
reciever not modified. Previously everything worked. Reciever log not contain 
any errors.
My app id CCDCBE66. My android app 
https://play.google.com/store/apps/details?id=ru.cn.tv

Original comment by v.sekret...@gmail.com on 19 May 2015 at 2:17

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

ust to clarify, in order to test Google Cast app one needs to publish (but not 
make it available to download) in the Google Cast Developer console - this 
makes the receiver available to all Cast devices. Another way to do it is by 
registering the device you wish to test on in Developer console and test with 
the app ID (if its your app ID). Further reference: 
https://developers.google.com/cast/docs/registration

Having said that, please let us know if your receiver is based on our reference 
receiver from Github? (https://github.com/googlecast/cast-custom-receiver) 

Original comment by na...@google.com on 26 May 2015 at 6:07