Bitten by the Test (Unpublished) channel bug
That's right...the test channel I use to proof my json feed is now affected by some Roku bug I have read others comment on. Previously, I was able to make updates to my test channel regularly. In t...
Forum Discussion
UPDATE: I took the nuclear option and created a second Test (Unpublished) channel. I renamed the original test channel feed file and uploaded it. I then used the new renamed feed file in my second unpublished channel. The channel starts up and briefly shows the location of where video items would display. It then immediately clears and all I see is a Search (Spyglass) button. Noting else shows in the channel.
Since the feed was copied from my original feed file used for the first unpublished channel, and, since that channel still displays correctly (even though I cannot update it), I'm left with the conclusion that there's a defect in the Roku framework that handles unpublished channels.
Coincidently, I believe that the use of the Search (Spyglass) button is new with the latest firmware update.
Do you use "The rest of the World" as your region? If you are located in the US just change it to the US.
I heard this problem from one of my viewers from another country. I contacted the Help Desk and They said they are no longer supporting "the rest of the World" region.
I will PM you my viewer's video.
I do not use Rest of the World. I have both test (unpublished) channels set to US.
I was able to convince Partner Success to look into this problem. Prior to this problem, I was able to update my test (unpublished) channel by updating my feed file and renaming it so that it would be ingested immediately. This always worked. It appears now from the following reply, that test (unpublished) channels are now subject to the same channel update procedures.
"We expect the 6+ hour mark if you do not perform a system update (or remove the channels and re-add them by code) because 6-8 hours is the ingestion time for the whole Direct Publisher system."
If the above is accurate, it now means that testing a channel will slow down the whole channel maintenance procedure. For example, you'll now have to wait upwards of 6+ hours to see if a change you've made in your feed file worked the way you wanted it to. This is not conducive to an effective work flow.
