Did you read the thread?! The solution has already been posted.
Yes I read. Please, can you simply suggest what code changes, I have to do and where to fix this error.
You must be new to development. One cant simply suggest what code change must be made without seeing your code. 🙂
Please study this sample. This implementation passes the static analysis tool and you can model your solution based on that.
https://github.com/rokudev/scenegraph-master-sample/tree/master/Subscriptions
Weird I'm using this exact way to create and handle channelstore but I'm still getting this error. I'm implementing a TVOD channel so my logic is from tvod-sample-master from here
https://github.com/rokudev/samples/tree/master/roku%20pay
I also have authentication built into the channel when user tries to play a paid content. I don't understand what could cause this issue
Its been a couple of months, so the exact details are sketchy.
I was following this sample to create the in app purchase (without login):
https://github.com/rokudev/samples/blob/master/roku%20pay/SimpleChannelStore.zip
After completing the app, I could not pass static analysis until I made the channel store node a global rather than a member variable.
m.global.AddField("channelStore", "node", false) m.global.channelStore = CreateObject("roSGNode", "ChannelStore")
Does anyone have example for Screensaver (RunScreenSaver())? I have tried to create and handle channelstore as suggested here but it's not working for screensaver case. Any ideas?
If you intend to handle in channel billing for a screensaver you will need to add a "RunScreenSaverSettings" entry point. This will available on the system screensaver chooser. Otherwise if you want the channel to be a one time purchase, just set it in the dev portal monitization option.
https://developer.roku.com/en-us/docs/developer-program/media-playback/screensavers.md
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!