"wcfray" wrote:
My telnet debug screen had numerous entries which I am still trying to look at, but one in particular baffled me: Manifest does not exist in zip archive.
One thing at a time, @wcfray!
(a) you had published a channel (private or public), which stopped working and
(b) now that you try to re-publish it, you are getting some additional issues (manifest complains)
I understand you want to fix the channels but trying to address everything at once will just confuse the matters.
What firmware is your player running and when has it updated last?
viewtopic.php?f=34&t=75717
"RokuJoel" wrote:
Make sure you zip from within the folder and not from the root - open the folder of your project, select all, and send to zip.
"wcfray" wrote:viewtopic.php?f=34&t=75717
The date on that topic is close to 2 months before I started having my problem.
"EnTerr" wrote:"wcfray" wrote:viewtopic.php?f=34&t=75717
The date on that topic is close to 2 months before I started having my problem.
I did not say your problem was caused by the beta firmware discussed there. Rather i pointed unexpected ways exist, in which new firmwares may break working channels - one of which is a change in a Roku-provided file used with "library" statement.
Isn't 5.5.410 a little old-ish, or is this the current fw for #3100, does someone know?
An idea on the side, Roku*: how about keeping a web-page or forum topic with list of all current firmware versions, per model? For easy reference when in doubt.
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!