Roku Direct Publisher

The easiest way to create a great TV experience.
cancel
Showing results for 
Search instead for 
Did you mean: 
hotwebideas
Level 7

All of a sudden: The feed format is invalid. We are unable to parse it.

Roku Support, what is going on? I used to publish my channels with the SDK which worked well, but ever since I switched to Direct Publisher, I seem to have more problems than ever and I am thinking of going back to the SDK.

Now, all of a sudden, two of channels' Feed Status page show The feed format is invalid. We are unable to parse it.  

I use the JSON feed. It parsed fine before this, so did anything change?
WordPress Interface to Manage Roku Direct Publisher
TVChannelPress.com
0 Kudos
4 Replies
37mediagroup
Level 9

Re: All of a sudden: The feed format is invalid. We are unable to parse it.

Try running it thru here:  http://jsonlint.com/  Is it possible something off in the coding. 
0 Kudos
hotwebideas
Level 7

Re: All of a sudden: The feed format is invalid. We are unable to parse it.

Thank you. JSONLINT reports it as valid. https://www.crazymoneyideas.com/roku/untapped/bestnewhiphop.json 
WordPress Interface to Manage Roku Direct Publisher
TVChannelPress.com
0 Kudos
Highlighted

Re: All of a sudden: The feed format is invalid. We are unable to parse it.

I don't know if this applies or helps. Did you make any updates to your Json file? I host mine on AWS, and I found that I too would get that error if I just uploaded and replaced the file. I literally delete my JSON file, immediately upload my updated file (same name) and then change permissions to worldwide.
0 Kudos
hotwebideas
Level 7

Re: All of a sudden: The feed format is invalid. We are unable to parse it.

"attilascreative" wrote:
"attilascreative" wrote:
I don't know if this applies or helps. Did you make any updates to your Json file? I host mine on AWS, and I found that I too would get that error if I just uploaded and replaced the file. I literally delete my JSON file, immediately upload my updated file (same name) and then change permissions to worldwide.


Thanks, @attilascreative, but I found the issue and it is solved, thankfully. The cause was that I recently added a SSL certificate to my domain name, so now I had to convert all of the http to https in my JSON feed and everything worked well. 
I actually did try your suggestion of using AWS, but not changing the http to https had the same issue  :twisted: Thanks for your help Smiley Wink
WordPress Interface to Manage Roku Direct Publisher
TVChannelPress.com
0 Kudos