Heya, so I'm rather new to all the Roku development (only been messing with it for a few days) and I wanted to create a screensaver based on the classic Minecraft panoramics. I completed my project and got to a point where I was happy with it while messing around with it. I decided it would be cool to later get rid of all of the copyrighted assets and publish it on the Roku store, but I ran into issues during the Static Analysis.
I keep getting messages regarding that channels are prohibited from offering in-channel screensavers, ("Channels are prohibited from offering in-channel screensavers or any feature that overrides the Roku system screensaver.") and how the channel type is apparently channel and requires Main() or RunUserInterface() even though it's not allowed for screensavers?
I'm confused as to if I've uploaded this correctly. I put classification on the properties tab as App/Utility and set descriptive catagory on the channel store info tab on Screeensavers. Is there something wrong with the way I've uploaded it or is there possibly something wrong within the manifest or code that's incorrect.
Here's the GitHub repo if that's any help: https://github.com/Animoun/VoxelPanoramicScreensaver
Any help is appreciated, thank you.
Your manifest is all wrong. Check out the "Required screensaver attributes" here:
https://developer.roku.com/docs/developer-program/getting-started/architecture/channel-manifest.md
Your manifest is all wrong. Check out the "Required screensaver attributes" here:
https://developer.roku.com/docs/developer-program/getting-started/architecture/channel-manifest.md
Yep you were right, thanks dude! Greatly appreciate it!
I'm trying to develop a screensaver app as well but feel lost because everything has to do with video and audio. Any pointers or tips?
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. You will not be able to log in or post new comments or kudos 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 12 and you may notice reduced functionality.
In the meantime, for additional assistance, visit our Support Site.
Thanks for your patience — we’re excited to share what’s next!