Roku Developer Program

[mgregor13]

Not sure this has been posted before, but after doing a few hours of dev on my dev enabled Roku 3, it started to not accept new builds.   It would hang on the step where it was uploading to server and then when I would hit cancel the error message said something like <meta refresh failed content=0 blah... > .     I had seen this before, but usually a power cycle on the device would fix this and I could then begin sending debug builds again.    In this case, when it didn't work, I took the next steps of hard power cycling by pulling the plug, restarting my macbook, and then eventually hard resetting the device.    That was a mistake as when I went back to the MyAccount and tried to re-link my now freshly reset Roku 3, the linking process was interrupted with an error on the web page flow.  I refreshed the page and it then said the device was linked and the device moved on like it was linked, but when I went to put it in dev mode, it said it wasn't linked.   I tried this multiple times and always got the same results.    Seems like something is broken on the site or with the linking process for the devices.

[Komag]

I would try to wait a bit longer and not do a cancel or refresh too quickly, that's always asking for trouble. But it sounds like in this case there is something more wrong that is not your fault.

[mgregor13]

Thanks for your reply.

For posterity the only thing I can add since the problem seemed to magically go away is that I did switch networks that used a different IP range but by then, approximately 2 hours later the device was magically linked and all my apps were downloaded. There seemed to be nothing wrong with the old network in any way for any other action. So who knows maybe it was the time. As far as waiting longer do you mean how long to wait for the http server on the device to time out? What do you normally see thrre? I see either 20 seconds or less or it just goes the whole 300 secs to timeout.

Thanks again...

[EnTerr]

When resetting the device, perhaps the weather was "cloudy, with chance of outage" and later the sky cleared?

Try not to have a channel running when uploading new one - historically there have been issues with that.

[mgregor13]

Hah!  I wish I knew.  

Good tip.  Sometimes it seems like the Export tool is unable to remove the old app and if I manually delete it it then allows a reinstall.  But in this case it was something different.

Upon sniffing the Box's http traffic it seems it needs to hit http://captive.rolu.com at the beginning of this install sequence.   Perhaps that was failing.   I wasn't sniffing HTTP at the time I had the problem, but I'll keep an eye on it.

[EnTerr]

"mgregor13" wrote:
Upon sniffing the Box's http traffic it seems it needs to hit http://captive.rolu.com at the beginning of this install sequence.   Perhaps that was failing.   I wasn't sniffing HTTP at the time I had the problem, but I'll keep an eye on it.

It does?
Huh, i don't think it should be doing that. It might be a side effect of them bastardizing the on-player HTML dev.pages a release or two ago - it was basically putting lipstick on a pig (and i for one hate lipstick on my ham) - but as part of that "beautification" some javascript monstrosities started getting dragged from the Web (WTF?)