Policy failed to download

[decadeofdefeat]

For some reason now I'm getting a looping error from QCPolicy.brs :

Policy failed to download: The requested URL returned error: 403 Forbidden

Is there a reason why this could be happening?

[SmithKevin]

Hmm thats odd. I will look into it now at let you know what I find.

[SmithKevin]

So I just confirmed that the policy endpoint is up and working so I have a few question for you.

1. How long was it working before you noticed this error?
2. What is your applications name so I can look up the API-Key you are using?
3. What Roku device are you running into this issue? Do you have multiple Roku devices to verify if it is only happening on one?

Thanks for the additional info.

[decadeofdefeat]

1. I just tested it today when I discovered a bug in my Roku channel, and discovered the neverending loop. I added QC about a year ago and haven't noticed an issue until today.
2. The app name is RokuApp, my network is The Chapel.
3. I'm using a 4200x. I don't have multiple devices right now to confirm it's just on this device.

The URL it's trying to load (quantcount.com/policy.json) does appear to load in my browser, so I'm not sure what the issue is.

[SmithKevin]

Interesting. The full URL it should be trying to call is (blocking out your API Key)
http://m.quantcount.com/policy.json?a=***-***&v=1_0_2&t=ROKU&c=US
which is loading properly on my side.

Can you verify that the above url works with your API Key? Also are you using the most recent version 1_0_2? You can find it in the Quantcast.brs file

[decadeofdefeat]

When I open the link in my browser, the page returns {"blacklist":[]}, so I believe it's working correctly. But in the Roku development app, I'm getting the Policy failed to download error. I'm not super concerned about this, so if we can't find the solution it's ok. Roku does have it's own analytics now which is nice. I disabled the infinite loop by commenting out the function call when it fails to load.

[decadeofdefeat]

Oh and yes it's 1_0_2

[SmithKevin]

Maybe it due to a software upgrade on Roku's side. Sadly I don't think there will be a quick solution. Thanks for the heads up and I will try to schedule some time to dig into it on the Roku box here.