Ok i uploaded two channels but neither are working for me.
the zip files work just fine here for me but after i package them and upload them and I add the channel, they aren’t working for me at all.
also i have a question about the packages, now i am worried cause i used the same terms in each for example “token” and stuff like that to write to the registry.
will they be recognized by each channel as the same or will Roku know they are for different channels and know where they go?
I am worried now they didn’t make the contest deadline cause for me they are not working
“dynamitemedia” wrote:
Ok i uploaded two channels but neither are working for me.
the zip files work just fine here for me but after i package them and upload them and I add the channel, they aren’t working for me at all.
What exactly do you mean by “aren’t working”? Do the channels not show up, or do they open and immediately close? Or is some specific functionality not working? If you used the same zip file for packaging as you did for testing, then they should behave the same.
“dynamitemedia” wrote:
also i have a question about the packages, now i am worried cause i used the same terms in each for example “token” and stuff like that to write to the registry.
will they be recognized by each channel as the same or will Roku know they are for different channels and know where they go?
If you used a different roRegistrySection name for each channel, then you should be fine. If you stored the data for both channels in the same roRegistySection, then they’ll overwrite each other.
“dynamitemedia” wrote:
I am worried now they didn’t make the contest deadline cause for me they are not working
If you just submitted the channels today, then you may have already missed the deadline. The deadline for submission was Monday night/Tuesday morning at midnight PDT. They allowed updates to submitted channels until 9AM this morning, but weren’t accepting new entries after the initial deadline… but I’ll defer to Roku on that one.
What exactly do you mean by “aren’t working”? Do the channels not show up, or do they open and immediately close? Or is some specific functionality not working? If you used the same zip file for packaging as you did for testing, then they should behave the same.
they just open and immediately close… yeah i used the same zip files, and when i am testing here they are both working just fine, just not the submitted versions
If you used a different roRegistrySection name for each channel, then you should be fine. If you stored the data for both channels in the same roRegistySection, then they’ll overwrite each other.
Hmmm, that could be a problem! i think i may have used the same, i basically made two of the same channels only changing what webUrl to go to get the XML
If you just submitted the channels today, then you may have already missed the deadline.
I submitted the original, these were just the updates
“dynamitemedia” wrote:
I submitted the original, these were just the updates
My understanding of the contest was that you could continue updating the submitted app UNTIL the deadline, at which point that was the final version to be used for the contest. Maybe your problems are related to the newer entries being submitted after the deadline?
“dynamitemedia” wrote:
I submitted the original, these were just the updates
My understanding of the contest was that you could continue updating the submitted app UNTIL the deadline, at which point that was the final version to be used for the contest. Maybe your problems are related to the newer entries being submitted after the deadline?
Actually, Patrick sent out an email yesterday…
We’d like to give you one final opportunity to make sure your channel is as good as it can be before voting begins. To that end, You have until 9AM PDT tomorrow, Wednesday September 8th to update your channels to get that final optimization, typo correction or feature in if you’d like. No new channels will be accepted, but you may update the package for your submitted channel.
“TheEndless” wrote:
If you used a different roRegistrySection name for each channel, then you should be fine. If you stored the data for both channels in the same roRegistySection, then they’ll overwrite each other.
If your channels are independent, you should be rekeying your Roku box and signing your packages with different keys. If you channels are signed with different keys, it doesn’t matter if you use the same roRegistrySection name.
“hoffmcs” wrote:
If your channels are independent, you should be rekeying your Roku box and signing your packages with different keys.
I understand that using the same key allows multiple channels to access the same registry info, which is handy if that’s a needed feature, but I’m not clear on why you say you “should” re-key for every channel…? In fact, the SDK documentation even suggests creating a dummy app to store your key for future channel development, which would suggest the opposite. I can see the utility in re-keying, if you’re developing channels for different clients, but I’m not sure why you’d want to otherwise. Am I missing something?
If you aren’t re-keying for each app, you must be careful of namespace conflicts. All apps with the same key will share the same registry and could therefore collide on writing the same keys in that registry.
And if you have a public screensaver and any of your apps have a private screensaver, you have to rekey. I don’t know whether if you only use private screensavers if they need different keys. Kevin?
When you select a system screensaver, the system chooses the first screensaver that matches that key. So if there are multiple screensavers signed with the same key the user can’t select between them.
“renojim” wrote:
And if you have a public screensaver and any of your apps have a private screensaver, you have to rekey. I don’t know whether if you only use private screensavers if they need different keys. Kevin?
-JT
It’s not an issue for private screensavers, since the local ShowScreenSaver function is called to launch those. At least it hasn’t been an issue in my apps, and I always assign a different “roRegistrySection” name to each channel based on the name of that channel, so they won’t step on each other. If you use a generic name like “Configuration” like the SDK apps, I can see where it could get a bit sticky…
so out of nowhere after it has been working now im getting these crazy issues
Current Function:
017: Function RegWrite(key, val, section=invalid)
018: if section = invalid then section = "Default"
019: sec = CreateObject("roRegistrySection", section)
020: sec.Write(key, val)
021: sec.Flush() 'commit it
022: End Function
/tmp/plugin/PEAAAAjZDDuq/pkg:/source/generalUtils.brs(20): runtime error 18: Typ
e Mismatch
020: sec.Write(key, val)
I have never touched this BRS pages settings
I have read the SDK and see no reference to this, its why the channel is not showing up, it was working when i went to work today i come home turn it on and even my original is doing this…
i would like to also know more about this rekeying…
Check that key and value are both strings. It doesn’t look like it has anything to do with what package signing key you are using (unrelated to the variable name key in this code snippet).
“dynamitemedia” wrote:
It seems it was a website issue, was passing a empty xml field… gonna have to do a check on those to make sure they send something…
That’s great news! Glad it’s something you can address without requiring a code update. Good luck!
