I sent my problem into Roku and they discovered a problem as well and it was sent over to the engineers. They deployed a fix. They have been great about staying in contact with me to provide updates. I'm still having one problem and waiting to hear back once more on the topic.

Normally, I am able to load a feed with changes using a different file name and it validates. But for over a week now when I load a feed onto that test channel it always gives me errors. If the same content in the feed is made into a new file with a different name, added to the server and then added...

After a friend helped me find a playlist in my feed that needed to be taken out (because it was not referring to any videos in the feed), it fixed the feed. But, it only validated in roku after setting up a new test channel. When the same feed is added to my original test channel, roku won't validat...

Just an update on chasing down the problem of the errors in case others have the same problem...I added tags to the series that were missing. Roku validation of the feed remains at the same 138 errors so adding missing tags and correcting the other tags made no difference to the number of errors.

Made a change to the date schema but roku remains at  ....so back to the drawing board again to track down the culprit :) ⋅  1 item has an error: No valid items were found in the feed: validate 07/11/2019 11:18AM ⋅  138 items have error: Required video details are missing or inva...

I read little bit ago that it was changed to 2020. Thanks again for helping.  I was thinking it might have been what the roku validation was saying about missing video details. So far I don't see any missing video details in that part of the json. I saw a file missing a bitrate so I added it but whe...

Thanks again. I'll try this and run it through the roku validation again. I guess it was a fluke that my json's have been passing all of these months / in some cases year with the other. Then, to difure out what in the world is causing the other 138 errors. I was finally able to get it to 138. Takin...

Perhaps it's this HDBifUrl parameter which I don't have implemented...

The date is the same format I have been using on this channel and the others up until last week it was working fine.  I've looked at the specs. I must be overlooking something then because I don't see what is missing.  I've been reviewing this    https://github.com/rokudev/feed-specifications/blob/m...

A note about "required video details".....

I don't see what is missing. I did see a bitrate was not on a video and I added it and then tried to validate the feed on roku to watch the error message to see if it would change but it remained the same. 

It's as if somehow I've copied part of an old json into my new one. So far that is the only explanation I can figure out as to how this file got messed up. I've corrected all of the tag errors so far except I'm trying to figure out what is meant by a category tag for series errors. I have a category...

Hi, I appreciate your help. This is so strange.the feed has been validating in roku week after week except this past week. it validated and is playing. the one with the new videos did not get added. i can;t wrap my brain around what has changed all of a sudden to give errors. I sure appreciate you d...

I agree it's easy to make a mistake. It's been very helpful to use the jsonlint and the json editor. I just now made a copy of the actual json feed that is currently working on the channel. Then, added this new copy to my server under a different file name, set the acl and using my test channel in d...

I'll double check the brackets first. Thanks for this tip. After I had the problem, I went back to the original feed that has been working for a week since I had made other changes. That feed had of course validated just fine a week ago with no errors so I figured going back to it before any changes...