Thank you. I appreciate the detailed response, these are the answers we need.
- Google chose to use different YT/YTTV platform app versions/builds for different Roku models/model types and/or RokuOS versions/builds, and created their own ongoing support nightmare.
Of course they did. Overcomplicating software is their thing.
As for Roku's CS agents/product managers interfacing with Google YT/YTTV RokuOS app developers/engineers/platform provisioning: This is relatively limited
I understand and appreciate this. It's nice to know if Roku makes contact like this. From the customer (my) point of view. That is more effective, by a long shot, than any of us reporting issues or providing feedback to Google/YT.
Google is a frustrating company to get support from. I've been struggling for a decade now to get them to fix the pin on Google maps for my home so deliveries don't get directed in the middle the street by my backyard.
My expectation of this getting resolved any time soon is - not likely.
Google is a very difficult company to get support from, unless/until you are using a paid for product/service, at which point CS becomes readily available (and often easy with credits/refunds, in lieu of actually fixing the issue most of the time).
You (and others impacted - numbers matter for this type of issue) will have to be persistent with Google/YT CS if you want it addressed, and considering RokuOS 14.6.4 is starting to roll out (most likely with new versions/builds of YT/YTTV) its liable to get lost in the shuffle/de-prioritized (again, persistency is key).
Otherwise in the meantime I suggest (obtaining and) using the YT client for another platform, assuming you have implemented a multi-platform streaming strategy (if you havent, you should, due to frequent occurences of this exact type of issue on one device/platform or another) - which can be achieved for relatively low cost: competing platform 4K/HDR models can be had for as little as $20-30 (ONN 4K Streaming Box/Plus) or $50-60 (Amazon FireTV Stick 4K Gen 2/Max Gen 2).
(Aside: I've also had issues with Google Maps addresses in the past, and for several years they wouldnt accept my repeated corrections: effectively an entire new subdivisions' addresses were either incorrectly pinned to the street I live on, or otherwise pinned to bizarre nearby locations other than the actual location within the subdivision), resulting in packages, confused drivers, and irate residents of the homes within the new subdivision appearing at the doors of my/neighbors' houses, until finally about 6 months ago they accepted my corrections for 3 of the "worst" incorrectly pinned addresses, at which point i then spent the time and submitted corrections for every other address in the subdivision (about 100 addresses total), which were accepted, and finally ended the years long package misdelivery nonsense for everyone)
