Confirmed via my web remote Remoku, re-launching fails while channel is running. I'm certain this is a change in behavior from earlier firmware releases.
"rjune11111" wrote:
I've seen messages on this forum claiming that an ECP launch of an already running channel app should re-launch that channel, but on my Roku 2 XS running v4.8 (build 1178), I'm seeing such launch attempts fail, for all channels. The POST gets back a 200 OK response, but the channel does not re-launch, the old invocation remains running (see below). If the channel is not already running, the same POST causes the expected launch to happen.
I can't remember for sure, but I think that re-launch used to work. Could this be a 4.8 regression? Thanks!
Launched Channel Store, scrolled down a few lines, then invoked the following. Channel Store did not re-launch.
$ curl -v -d "" http://192.168.20.111:8060/launch/11
* About to connect() to 192.168.20.111 port 8060 (#0)
* Trying 192.168.20.111...
* connected
* Connected to 192.168.20.111 (192.168.20.111) port 8060 (#0)
> POST /launch/11 HTTP/1.1
> User-Agent: curl/7.24.0 (i686-pc-cygwin) libcurl/7.24.0 OpenSSL/1.0.1c zlib/1.
2.7 libidn/1.22 libssh2/1.4.0
> Host: 192.168.20.111:8060
> Accept: */*
> Content-Length: 0
> Content-Type: application/x-www-form-urlencoded
>
< HTTP/1.1 200 OK
< Content-Length: 0
< Server: Roku UPnP/1.0 MiniUPnPd/1.4
<
* Connection #0 to host 192.168.20.111 left intact
* Closing connection #0
