Tim109
As previously stated, Roku is not avoiding responsibility.
I'm possibly their biggest critic.
And 2 seconds looking into this issue shows it's on the app side. You've seen the posts on github explaining it. I don't know where the disconnect is.
From Github: "HTTP ERROR CODE 429 error is due to Google API rate limiting the application. Sometimes we have people that use up all the millions of available API requests for this application and impact others.
Count resets at 12:00 pm PT from Google side. Nothing we can do from the application side. This is why we "try" to limit API requests as much as possible in the application."
According to Github, it's not even an OS-side problem, this couldn't be further from Roku's fault. It's not even the fault of the app on your system, rather how it's being handled by servers on Google's end.
"Surely they would know more about it than me. I would have thought anyway."
Yes, we do, and we're telling you that for once it's not Roku's fault, there's nothing you can to do address this issue from the Roku/OS side.
Where are you even getting the idea that this is Roku's problem?
This is a problem within the app. There's nothing complicated about that.