Forum Discussion

jacksonp2008's avatar
jacksonp2008
Reel Rookie
5 years ago

Unexpected results from tutorial

Team Roku, 

Just now tuning into this platform and it looks like it has a lot of potential for us.

I tried your tutorial here:  https://developer.roku.com/docs/direct-publisher/tutorial/feed-url.md

And loaded up this one:  https://d3pvdvkqj4l2t6.cloudfront.net/RokuDevelopers/rdp-content-feed.json

It seemed to work, created this https://my.roku.com/account/add?channel=QRHDJX

However, when I view it on a ROKU, all it shows is a SEARCH, INFO and not much else.

If I can get a working example, I think I can take it from there.

Thanks, 

 

Roku Direct Publisher

5 Replies

  • sattun's avatar
    sattun
    Roku Guru
    5 years ago

    Hi,

    Roku Direct Publisher is a great product and its free, but it has its limits and drawback, one of them is that it takes hours for the new content to update and it's very hard to troubleshoot.

    You will be spending a lot of time to troubleshoot if you are creating your content feed by hand, and you are not familiar with RDP.

    That said, If you want more robust solution to manage your content feed for RDP, then I would recommend our OTTfeed.com platform, it was designed to solve this exact problem and much more.

    Also, We have custom Roku app that is similar to RDP but with more features, I plugged your feed and it looks good (see screenshot below).

    To get more info about our custom Roku app go to: https://ottfeed.com/roku

    To get more info about our OTTFeed management system, request a demo at: https://ottfeed.com/

    Thanks, 

    • jacksonp2008's avatar
      jacksonp2008
      Reel Rookie
      5 years ago

      I have no problem writing code to generate json, I just need an example that actually works.

      If your solution is free, i'm willing to take a look at it.

      • Baradanikto's avatar
        Baradanikto
        Roku Guru
        5 years ago

        jacksonp2008 

        However, when I view it on a ROKU, all it shows is a SEARCH, INFO and not much else.

        There are two potential issues happening here.

        1. It takes upwards of 6 hours for Roku to ingest a json file and make it active.
        2. A search of this forum will reveal that other developers have reported the same issue.  If you still have this problem, contact Roku Partner Success.  They should be able to fix the issue.