If you ask me whom to press for this, it would be Netflix. We have a "resolver" issue, which is likely introduced by Google TV and Cast SDK itself, and we have a deeplinking issue, which is very confidently likely introduced by Netflix. Whatever the problem is, this is purely with the Netflix team and the way how they implement/use Chromecast protocol to communicate between sender/receiver devices. Oh yes, also it could be that there is a crappy implementation of the deeplinking too which fails at multiple stages (personally for me, I get Neflix opening, but never playing the content I required). The second issue, which is the direct reference to the op's question, is why we need to enter pin or log in within the app? The answer is simple: it is the lack of required metadata coming from the sender device, or its incompatibility with the deeplinking parameters required by the local app (the one on the dongle). A potential solution to this problem which I'm contemplating on now is to uninstall Netflix from the "dongle" and see what happens. In other words, Chromecast will not pull a dedicated application from Chromecast server, but just launch the local one. First, when receiver gets a cast information it actually makes a "hardwired" choice to launch the application which is already installed on the Google TV device. Now, my feeling about Google TV and Netflix is that there's two issues, quite separate though. In fact, this was available from day one of Chromecast technology, which was obviously designed to pass any required metadata to seamlessly pull a receiver app and launch it without user having to input anything (because back in the time there was no input at all in CC, right?). The truth is, it is possible to pass the associated user information when launching (casting) an app from sender device. Perhaps there is a proxy app that can announce itself to be Chromecast and forward to the built-in Chromecast?Īs an engineer/manager from the connected television domain, I actually worked with cast quite a lot technically. Would be nice if we could make the Chromecast app disable this app link feature and have Netflix resort to proper Chromecast casting. Finally I got the message that Netflix gives no guarantee that any feature works. ![]() They will forward it to the development team.Įvery other app is able to cast to Google TV, except for Netflix. Netflix apparently requires the Netflix app plus same account on the target device of the Chromecast app is being targeted (contrary to a dedicated Chromecast device).Īpparently Netflix support have no idea that that is how their system works which made is waste a lot of time debugging this without a resolution. ![]() I have the same existence as everyone in here but thanks to your comments, I now know why it doesn't work. I just spent 1,5 hours with Netflix support to get this to work, but it didn't work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |