"kevintwister" wrote:
Anyone understand "Channel under test doesn't share linking info with channel from channel store"?
"squirreltown" wrote:"kevintwister" wrote:
Anyone understand "Channel under test doesn't share linking info with channel from channel store"?
It could mean many things. Maybe the wrong dev id is being used to pkg and users saved/store info is not being found.
"Veeta" wrote:
You need to keep the same developer id+password for the duration of a single channel. The dev id is tied to a number of things, but most obviously the registry entries on the users devices. If you change the developer id, you won't be able to read registry entries you had previously written (e.g. authentication info). It may be that previous versions of your channel got through with different dev ids but this is not how most channels are managed.
You need to persist 3 things when you provision a new channel:
1) Developer ID from running 'genkey'
2) Password from running 'genkey'
3) Any signed package from the device with the above developer id
This way you'll always be able to "rekey" a roku device to allow it to sign new packages with the same developer id as your original package.
"RokuMarkn" wrote:
jmss82 says they lost the password, so they can't do a rekey. In that case, their only option is to publish the channel with a new key. This means that all users will lose any data stored in the registry. How serious that is depends on how the channel is written. It could mean no problem at all (if the channel doesn't use the registry), or it could be a big problem for their users (if valuable nonreplaceable data is stored in the registry).
--Mark
"kevintwister" wrote:
The odd thing is my lead developer (jmss82) has been using different devices for 2 years to create packets which he is telling me has always generated a new key depending on the device. We have submitted several updates in those 2 years. Your QC guys have never noticed or mentioned it before and it's why we got confused with this last submission.
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!