mmeitine / google-cast-sdk

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

Cast request ends in error using iOS SDK 2.7.1 #612

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi,
After upgrading the iOS SDK to v2.7.1, casting DRM-enabled videos fails after 
the license request with the following error in the Chrome Debug Console:

Uncaught InvalidStateError: Failed to execute 'webkitAddKey' on 
'HTMLMediaElement': No media has been loaded.

This comes after a 200 OK response for the license request and the debug 
console outputs: [cast.player.core.MediaKeySession] xhr success

Downgrading the iOS SDK to v2.7 without making any changes to either the iOS 
sender code or the receiver code resolves the issue.

I would like to use the latest version of the SDK, but the changelog only 
mentions a fix for setting activeTrackIds to nil, which I'm not doing, so I 
don't know what else to change in my code to make it compatible with v2.7.1.

Reproduced on iPhone 6 running iOS 8.4 & iPhone 6 running iOS 8.3
Google Cast iOS SDK v2.7.1

Original issue reported on code.google.com by rapp...@gmail.com on 8 Jul 2015 at 10:53

GoogleCodeExporter commented 9 years ago
Also note that casting non-DRM protected videos using the iOS SDK v2.7.1 and my 
same sender + receiver codebases does not reproduce the issue, the videos are 
playing back fine.

I'm using PlayReady DRM protection, which is the only scenario causing a 
failure for me through SDK v2.7.1.

Original comment by rapp...@gmail.com on 8 Jul 2015 at 11:01

GoogleCodeExporter commented 9 years ago
Please provide receiver logs and Chromecast firmware. 

Original comment by na...@google.com on 9 Jul 2015 at 11:15

GoogleCodeExporter commented 9 years ago
Are you still facing the issue? Please provide required information if so. 

Original comment by na...@google.com on 17 Jul 2015 at 5:25

GoogleCodeExporter commented 9 years ago
Closing this issue since there is no response. Please report back with required 
information if you are still facing the issue and we'll reopen it.

Original comment by na...@google.com on 12 Aug 2015 at 5:51