Roku Developer Program

[fortscan]

Have any other developers -or Roku- noticed that the redirection which was recently implemented from owner.roku.com to my.roku.com broke the traditional method of adding private channels via a direct link?

Previously, the sequence was as follows:

1) The user would access:
https://owner.roku.com/add/{channel-code}

2) The request would be redirected to the login interface while preserving a reference to the previous linking URL and channel code:
https://owner.roku.com/Login/?ReturnUrl=/add/{channel-code}

3) The user would submit the credentials.

4) After validating the credentials, a redirection would finally take the user to:
https://owner.roku.com/add/{channel-code}

This workflow is currently not working, since there appears to be no ?ReturnUrl querystring added right after step 1), when the request is now redirected by default to my.roku.com.

In other words when someone is asked to enter owner.roku.com/add/{channel-code}, the generic user interface from my.roku.com is shown instead of being taken to the actual installation of the channel.

While channels can still be added by manually going to the "Add Channel" link within the main account interface, the direct link method is widely used by thousands of channels and had become a standard reference to let people more easily complete the process.

Feedback on this issue from other developers and/or Roku would be greatly appreciated.

[fortscan]

In addition to the previously reported issue, end-users have also been reporting the following 2 issues since the redesign/update from owner.roku.com to my.roku.com took place:

1) Even when manually adding a channel (i.e. as opposed to using the direct URL link) by going to "Add a Private Channel" from the client interface, the confirmation message mistakenly assumes that all channels are paid channels and reports (even for free channels):

Channel {channel-name} has been added to your home screen, but will need to be purchased before it will work. Channel purchases are made from your device and require a valid payment method associated with your Roku account.

This is extremely confusing for the end-user, who just came from a previous screen that clearly stated that the channel was free, and now suspects he/she will be charged for it by Roku.

2) Roku seems to have removed or hidden the "Remove Payment Method" link which was always available at the payment method update screen from the customer interface. This was even referenced in an official FAQ:

http://support.roku.com/entries/387912-How-do-I-remove-my-payment-information-from-my-Roku-account-


Feedback from Roku would be highly appreciated.

[TheEndless]

I'm not seeing either of the issues you're reporting here. The https://owner.roku.com/add/{channel-code} still works the way it always has for me, and free channels aren't showing the "will need to be purchased" message. Maybe it's a browser specific issue. I'm using Chrome, you?

[fortscan]

Thank you for your feedback!

It's not a browser issue, we actually tested it in all major browsers before reporting it.

The difference is that you are probably testing it while being already logged in to your Roku account.

You can perform the following test:

1. Logout from your Roku account
2. Click https://owner.roku.com/add/nautiluslive (completely random channel I just picked)
3. You will be redirected to my.roku.com in order to submit your credentials
4. Once the credentials are validated, the default user interface page will be displayed, instead of the actual channel linking page.

You can also replicate the other issue (free channels reported as requiring a payment) with the following test:

1. Once logged in to your Roku account, click on the "Add a Private Channel" link from "Manage Account" section.
2. Enter any sample code and confirm the installation
3. You will notice that the "Channel Added" message mistakenly informs that the channel needs to be purchased.

Below is a sample screenshot of the message:
http://awesomescreenshot.com/02f4qesnab

The workaround we identified for the first issue (default linking URL format not working) is using the following format for the linking URL:
https://my.roku.com/account?next=https://owner.roku.com/add/nautiluslive

Here the manually added 'next' query string is basically doing the same as the previous 'ReturnUrl' was doing at owner.roku.com. In other words, it's allowing the end-user to login in one page while at the same time retaining a reference to a second page where the end-user should be taken inmediately after login.

However, using this approach with the 'next' querystring manually added to the URL (as opposed to automatically detected by Roku) is clearly inconvenient and it would only be useful by mapping a third-party short URL to it.

A definitive fix could be implemented if the 'ReturnUrl' query string was added as a variable that the my.roku.com deployment was able to recognize for requests originally redirected from owner.roku.com, therefore taking the end-user back to the channel installation page after the login process is concluded at my.roku.com.

[squirreltown]

"TheEndless" wrote:
I'm not seeing either of the issues you're reporting here. The https://owner.roku.com/add/{channel-code} still works the way it always has for me, and free channels aren't showing the "will need to be purchased" message. Maybe it's a browser specific issue. I'm using Chrome, you?

I thought this too, and then today I tried logging out ( like most developers i suppose i logged in a couple of years ago and have not had a need to log out) and i tried a link i have on my web site and it of course asked me to log in and then forgot where i was going, it just took me to my account page. If i'm already logged in the web site link works like it always has. I'm using Chrome too.

This thread was started 48 hours ago, perhaps someone with Roku in their name could respond, I'd like to know whether I need to do this work around thing or if it will be fixed.

[RokuJoel]

Our web services teams are (now) aware of the issue and we expect a fix to be pushed on Tuesday.

- Joel

[squirreltown]

"RokuJoel" wrote:
Our web services teams are (now) aware of the issue and we expect a fix to be pushed on Tuesday.

- Joel

Thanks Joel.

[fortscan]

Thank you so much for your feedback!

[destruk]

Would you be able to fix the displayed data too - for channels?
This doesn't look very good -
"ASDomain_Data_Channel_ParentalHint_AllAges
ASDomain_Data_Channel_AdditionalRequirements_AdditionalFeesMayApply"

[bosborne]

This is still not fixed, is it?