Styled Media Receiver tears down on automatic iOS Disconnect

[GoogleCodeExporter]

In the most recent Styled Media Receiver update mentioned here:
https://plus.google.com/117916055521642810655/posts/EfDXA8N6dM3

There is a regression for any iOS apps that use the Styled Media Receiver. 
Basically tapping the home button, or locking the screen while casting content 
causes the SDK to auto-disconnect and the receiver to tear-down completely. 
Previously it kept playing.

What steps will reproduce the problem?
1. Start casting content from an app that uses the Styled Media Receiver (eg: 
Pocket Casts) on iOS
2. Press home button on phone
3. Receiver stops content and tears down

What is the expected output? What do you see instead?
What should happen is that the content should keep playing, since the iOS SDK 
doesn't give developers an option not to disconnect on the app being 
backgrounded. This is a regression from the previous build of the Styled Media 
Receiver that kept playing on auto-disconnect of the iOS SDK.

Not to dramatise the issue, but this affects the version of our app which is 
currently live in the iOS App Store and is generating a lot of support 
requests. It worked when we tested it before shipping to Apple last week, now 
without any code changes at our end it no longer works.

Original issue reported on code.google.com by rustysh...@gmail.com on 12 May 2014 at 8:12

[GoogleCodeExporter]

Got same issue using chrome cast SDK 2.1.0 build 529. with iOS 7.0
My application is based on video streaming & while casting video to chrome cast 
device SDK auto disconnects the session & receiver also stops.

Steps to reproduce the problem:
1. Connect application to a chrome cast receiver device.
2. Once successfully connected with Cast Media receiver, play the streaming 
video.
3. Video starts to cast. 
4. Press home button/ power button of iPhone/ iPad device.
5. Chrome cast receiver stops the receiver application. So video streaming/ 
playing on chrome cast stops.

So, two issues raise here:

1. Even if my sender app goes into background, receiver should keep on playing/ 
streaming video unless I pass pause/ stop or disconnect to receiver.

2. If, due to any unexpected error receiver goes down/ stops working. Sender 
should be notified in time, so that proper handling can be done at sender's 
end. There is a callback, device didDisconnectWithError but its time out is too 
much and as my app is video streaming based so it hampers user experience.

Original comment by abhinavs...@gmail.com on 12 May 2014 at 1:01

[GoogleCodeExporter]

Can you verify that if you have a second iOS device connected and the app is in 
foreground, then that issue doesn't happen (number 1)?

Original comment by anad...@google.com on 12 May 2014 at 3:26

[GoogleCodeExporter]

Closing issue

Original comment by anad...@google.com on 20 Jul 2014 at 10:41

• Changed state: Invalid