Linked by Thom Holwerda on Mon 26th Aug 2013 16:24 UTC

Update: the functionality used by the application was reverse engineered and Google stated that it may change. Google has released a statement which acknowledges that playing local content will come back to ChromeCast once the API has stabilised. Storm in a teacup, apparently.

Heads up. Google's latest Chromecast update intentionally breaks AllCast. They disabled 'video_playback' support from the ChromeCast application.

Given that this is the second time they've purposefully removed/disabled[1] the ability to play media from external sources, it confirms some of my suspicions that I have had about the Chromecast developer program: the policy seems to be a heavy handed approach, where only approved content will be played through the device.

A company intentionally disabling cool stuff? Surely you jest.

Permalink for comment 570666
To read all comments associated with this story, please click here.
Member since:

Private API justifications are only made for Google when Microsoft is on the receiving end.

We all know you love Microsoft but why should you use every opportunity to try to make it look good?

Did you read the article? Who said was anything private involved? Please, go back and read it again. The API is not ready and prone to be modified and there was a warning about it, not less, not more.

Perhaps, you have some information that you could share with us, in which case I am all ears.

Reply Parent Score: 2