Well, I don't know where you live.
It's probably not available in your region.
I'm just a guy trying to be more helpful than Roku is, sorry!
Middle England
Hi @Tim109,
Thanks for the follow-up.
If this is the only app causing you trouble and you’ve already tried all the troubleshooting steps, it might be best to contact app support. We recommend contacting app support, as Roku channels are maintained by their developers.
Let us know if there’s anything else we can help you with!
Roku Community Team
So I'm looking at the Roku website and their seems to be no icons for app support. I presume you mean going to the actual app developers . So I've been to the photoview website and clicked on the support tab.
Just a cursory glance at the photoview app support page is telling me that a lot of people are struggling with this 429 error. (see link)
Tim, I'm the first to call out when Roku is avoiding responsibility, but this has nothing to do with Roku.
No one here can help.
This is a problem for the developers of the app.
If you're on github, I'm confused why you don't reach out to them instead of coming back here?
Yo i’m having the same issue! & By the way BEFORE this “new update” which didn’t seem to actually change anything besides having all these new errors all of a sudden, The app worked FINE! & It’s not just the app specifically it’s something with Roku on their end because this isn’t the only app with this issue. PEVAC for onedrive also is now popping up with these errors. Before the new update everything was fine. Can i downgrade or something and go back? This new update might be the worse unnecessary update i’ve ever encountered with anything ever .. All the hype saying how big this new update was going to be and so far everything is the same besides all these new problems it’s so annoying
But see the post before yours and it seems Roku want to wash their hands of it. I have heard that there is or has been some sort of dispute between google and Roku. The exact details of which, I cannot be sure. I'm not sure if I can do a total reset on my roku box where you delete the updates.
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.
Getting same error code
frustrating. Is there any other apps that are similar?
https://photostreams.roku.com/index
Yes, that's what most switched to.
However, it's having its own issue right now, randomly logging people out of their google account weekly or so.
In reality, there's no good option. I use Plex for photos but that's not integrated into a cloud account, it syncs with local files stored on my server.
We’re upgrading Roku Community to bring you a faster, more mobile-friendly experience. You may notice limited functionality or read-only access during this time. Read more here.
Planned Downtime:
Community will be unavailable for up to 24–48 hours during the upgrade window during the week of May 19th and you may notice reduced functionality.
In the meantime, for additional assistance, visit our Support Site.
We're sorry for this disruption — we’re excited to share what’s next!