Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • Does that happen with a Styled or the Default receiver, too?
    – Ali Naddaf
    Commented Mar 20, 2017 at 15:42
  • Actually, with a styled media receiver I only get the log statement "[cast.receiver.MediaManager] Load metadata error: [object Object] cast_receiver.js:67". According to the network tab in Chrome dev tools there's only one network call towards the stream and it returns HTTP 200. The receiver does not play anything, but it does not freeze and it still lets me disconnect.
    – Roy Solberg
    Commented Mar 20, 2017 at 20:04
  • I suggests you open a ticket on our sdk issue tracker and include a sample stream that can produce the result.
    – Ali Naddaf
    Commented Mar 20, 2017 at 21:11
  • Thank you, @AliNaddaf. I'll do that. I'm just trying to get verified that the server software is up to date and should be able to work and that everything is set up as it should be. However, I have now added more header and body info. You don't happen see anything suspect, do you?
    – Roy Solberg
    Commented Mar 21, 2017 at 14:05
  • Nothing jumps at me
    – Ali Naddaf
    Commented Mar 21, 2017 at 15:49