Roku Developer Program

[EnTerr]

Use of ECP "/launch/11?contentID=xxx" as a way of linking to a channel info page has been documented, advocated and used for a while

6. The following command will launch the channel store app (11) on the box with a contentID equal to 14 (the MLB app). You can get the plugin ID for your app using the /query/apps example above. It returns the installed apps on a Roku box. This technique would be useful in creating clickable ads in a free "Lite" version of a paid app. When a user clicks on the ad, the channel store page to purchase the full version could be launched.

$ curl -d '' 'http://192.168.1.134:8060/launch/11?contentID=14'

But today i noticed this does not work in fw 5.4.271 - plus server responds 404 (not found). Works fine in 5.3.4016 so seems this is a new development.

Has (hidden) channel 11 been removed intentionally? How is linking to a new channel/channel-info-page to be accomplished?

[RokuJoel]

Shouldn't be, I'll check.

- Joel

[RokuJoel]

Are you sure you are b271 and not 231?

Please try using this syntax in your curl command instead:

curl -d "" http://10.8.5.94:8060/launch/11?ContentID=14


- Joel

[EnTerr]

"RokuJoel" wrote:
Are you sure you are b271 and not 231?
Please try using this syntax in your curl command instead:
curl -d "" http://10.8.5.94:8060/launch/11?ContentID=14

$ curl -i -d "" http://192.168.1.25:8060/launch/11?ContentID=14
HTTP/1.1 404 Not Found
Content-Length: 0
Server: Roku UPnP/1.0 MiniUPnPd/1.4

It's build 271 all right, on 3100.

[RokuJoel]

Ok, thanks, looking into it on a 3100

- Joel

[RokuJoel]

Ok, I've been able to verify this issue on several 5.4 builds and have filed a bug report.

Thanks for finding this issue.

- Joel

[EnTerr]

Can you add regression test for that?

Maybe attach request to the bug ticket: test suite/script automation to call `curl -i -d "" http://TESTBOX:8060/launch/11?ContentID=12` and make sure gets HTTP 200 back (yeah, that does not guarantee it showed on screen but will detect failed call/regression).

[EnTerr]

Seems it was fixed in 5.4.3041