Roku Direct Publisher

[outinthebg]

I have updated my json file and URL location with a liveFeed m3u8 link
URL: 

I tested it the other day before planning to launch and it worked fine, Roku ingested the feed and everything. I literally haven't changed anything and now it's been trying to ingest/process this URL Feed for over 24 hours and still get this message: "The service is still processing your feed. Please check back again for updated status."

I have seen this before, but the longest I have ever had to wait is a few hours. Never an entire day!

[outinthebg]

Here is the json url

https://outinthebg.s3.us-east-2.amazona ... yjson.json

[Baradanikto]

Your feed file appears to contains errors.  There are several of these messages when I try to validate it.

2019-08-18 10:51:07.5300 ERROR Input string '1328.0' is not a valid integer. Path 'series[0].seasons[0].episodes[0].content.videos[0].bitrate', line 1, position 1262.

The 'bitrate' field is an integer, not a float.

[outinthebg]

I fixed the bitrate errors.. but before I fixed them I just updated the json and it finally ingested and updated the channel. Not only was the JSON URL updated but so was the layout and category names. Everything was working fine.

Now, all of a sudden.. even though it shows the correct published version and Feed URL, on devices it has reverted back to a previous state. It has old videos, my old layout and old category names. Very weird, even though when I go into the developer dashboard, everything shows the new information as the published version.

NEW FEED URL: https://api.myjson.com/bins/8ze33

It shows version 38 is live but it is like its now looking back at version 36 the way the channel shows on the device. I updated Roku, uninstalled and reinstalled the channel... still nothing.. looks like the old version even though it says it is not. 

[Hightek]

Well, this is what I do  each time I face such issue. I go to properties, I will then move back to the feed status, by then, it will bring the recent update