Feed URL Validation Error

The extension has nothing to do with anything. However, some web hosting providers are smart enough to assume that a ".json" file applies to a Content-Type of application/json, and serve the content with that Content-Type.

What's important is the HTTP Content-Type header returned by the server. It appears that Direct Publisher is looking for a specific Content-Type header of application/json, for example.

I don't know anything about Amazon S3, but when researching this problem trying search for "Content-Type" http header (sometimes also referred to as a mime-type). Look for a way you can specify a specific Content-Type for a particular file or file extension, either from a control panel or settings value, or some other url that will serve the same content with a different Content-Type. You'd probably get better help on StackOverflow under the 'amazon-web-services' and 'amazon-s3' tags.

belltown,

Thanks for the reply.  It was just enough info to point me in the right direction.  I figured out the problem and have corrected it.  Here's the jist.

When uploading a JSON file to Amazon S3, the content type does not default to "json".  I had to add that as a bit of meta data as part of the upload.  Their interface allows you to make changes to the meta data as part of the upload.

Unfortunately, that has not fully resolved my problem.  I now get a cryptic message:

The feed URL(s) could not be validated.
JSON (SyntaxError: Unexpected token � in JSON at position 0)

from the Roku portal when trying to validate the feed file.  And, as I stated, the file validates fine through the online validaters.

It looks like you're making progress. If you or the Roku DP uploader is seeing a strange-looking character or two at the start of the file, then you need to check the file's encoding.

I would imagine that DP expects the Json files to be encoded in UTF-8 without a Byte-Order Mark (BOM). It's possible you have a BOM at the start of the file. That may be a result of the way the file was encoded before you uploaded it (especially if you're on a Windows computer using certain text editors), or as a result of the way AWS is choosing to serve the file. First, what OS and text editor are you using to generate your .json file. Second, is there anywhere in your AWS control panel that you can specify an encoding (sometimes called a "charset") for the file? If you can specify an encoding somewhere in the AWS control panel/meta-data, etc., then set it to "UTF-8".

On a similar note, I keep getting this error message:

The feed URL(s) could not be validated.

There was a transport-level error - (Unknown ERROR).

I'm no JSON coding expert, but the JSON formatter says my code is valid.  Any idea how to remedy (or links to other threads that might assist)?
Thanks.  🙂 

"Baradanikto" wrote:
belltown,

Thanks for the reply.  It was just enough info to point me in the right direction.  I figured out the problem and have corrected it.  Here's the jist.

When uploading a JSON file to Amazon S3, the content type does not default to "json".  I had to add that as a bit of meta data as part of the upload.  Their interface allows you to make changes to the meta data as part of the upload.

Unfortunately, that has not fully resolved my problem.  I now get a cryptic message:

The feed URL(s) could not be validated.
JSON (SyntaxError: Unexpected token � in JSON at position 0)

from the Roku portal when trying to validate the feed file.  And, as I stated, the file validates fine through the online validaters.

Just a thought to help troubleshoot.  Try hosting the file at myjson.com and see if it passes the Roku checklist validator. That will at least let you know if its a file error or Amazon S3 specific. Secondly, some people mention the Header section of the feed?  Try checking the sample Roku feed and just paste that into yours again (provider name, language, last updated etc).
Just a thought.

I've made some more progress.  I was able to upload the json file specifying a different content-type of "application/json".  However, this only helped a little.  I still get the "unexpected token" error message "at position 0", but, it no longer has a funny character in the message.  I'll assume that the content-type correction helped that.  

I took some advice and used myjson.com to try my feed and it spits back I have "no valid items in my feed".  And, "27 items have error: Required shortFormVideo content is missing."  I've validated the syntax using the online services.  Is there a specific schema just for Roku validation?  Pasnow makes reference to a "Roku checklist validator".  Where is that?  Is that one of the online services that Roku recommends to check your syntax?  BTW.....my feed does include "shortFormVideo" tags and "content" tags.  The only potential discrepancy I see is the order of my json tags.  Does anyone know if the order of the tags is significant?  For example, my header contains a "providerName", but, it's not the first tag.  I would hope the order of the tags is NOT significant.

Lastly, I posted on the Amazon S3 forum because I may have found that they will not serve json files.  It appears they may only server xml.  I've asked for someone to clarify that.  I'll report back on that when I have an answer.

Oh, I forgot to mention, I wrote a powershell script that converts my xml feed to json.  It runs on Windows 7.

To remove problematic characters in your json file tun this regex to remove them, then save the result --
in php --
$json=json_decode(preg_replace('/[\x00-\x1F\x80-\xFF]/','',$source),true);

Where $source is the contents of your input file.

Having same error as Baradanikto.  Validator says JSON code is valid, but Roku direct-publisher repeats error message:  "No valid items in the feed."
Very discouraging after spending lengthy amounts of time trying to get it right.  Stuck like he is--any thoughts appreciated.

Does it give anything below it?  Like "No valid images in 1 feed" or something? Also check to see if the top header content begins similar to the Roku sample feed. These are just guessing but maybe double thru some of the semantics.  See if a paste into a myjson.com url works? Could it be a file format issue? 

I think I may have found the cause of my error.  But, I think I'm going to need someone from Roku to explain this.  My Powershell script converts my MRSS xml feed to a JSON feed.  In the process, it converts the "Content" object of the shortFormVideo object as a regular key/value pair which results in a "[" in the resulting JSON.  Looking at the feed specification, I noticed that the content object does not seem to conform to the specs like the other "objects".  It actually uses a "{".  So, while my code looks like:

"content": [
                {

The feed specification shows it as:

"content": { 

with key/value pairs.  I don't quite understand the discrepancy and why the "content" object does not behave syntactically like the other objects.  And, the reason this is a problem for me, and, possibly others, is that I can use a Powershell command called ConvertTo-Json that allows me to automate the creation of the Json file from key/value pairs.  This discrepancy breaks that command. I'm currently in the process of validating my suspicions, but, I'm stuck in "The service is still processing your feed". 

I'd love it if someone from Roku could comment on this.  I'd like not to have to create the Json by hand.