Are you, by any chance, displaying an “please wait” style message dialog when issuing the ECP command? I had issues with that when the Roku 3 was first released, and “fixed” it by removing the wait dialog.
In other words, just doing this ncat command from an external device crashes the box (as long as it is in a channel when the command is sent, and not sitting at the home screen). The IP of the Roku box is 192.168.0.29 in this case:
The following is an example command sent via the ncat command. It will launch the channel store app (11) on the box with a contentID equal to 2285 (the Hulu Plus app).
I’m not seeing that behavior at all. In fact, one of my channels uses that ECP feature extensively (https://owner.roku.com/add/MyChannels). I’ve never had it crash, and I’ve not received any reports from users experiencing crashes.
What’s the full version of the firmware you’re seeing the issue in?
I just took a look at your MyChannels app. It does not appear to launch the Channel store app to a specific channel’s detail screen. It just launches to it’s main screen.
Again, the bug occurs if you go from app1 to a specific detail screen within the Channel store app (by specifying a contentID).
It is very easy to replicate. Go to your Roku. Enter the Netflix app. Then do the POST indicated above to make it navigate to the Channel store screen for the Hulu Plus app (or any other app).
“roquoonewbie” wrote:
I just took a look at your MyChannels app. It does not appear to launch the Channel store app to a specific channel’s detail screen. It just launches to it’s main screen.
Again, the bug occurs if you go from app1 to a specific detail screen within the Channel store app (by specifying a contentID).
It is very easy to replicate. Go to your Roku. Enter the Netflix app. Then do the POST indicated above to make it navigate to the Channel store screen for the Hulu Plus app (or any other app).
I didn’t realize it was specific to the channel store, but I did try the POST you indicated above while in the Netflix channel, and still didn’t get a crash. I’m running 5.0b8043 on a Roku 2 XD.
“roquoonewbie” wrote:
did your test POST take you to the Hulu Plus page within the Channel Store?
It did. I tried it several times with the same result.
The box resonds to the POST with a 200 OK, and it does launch the channel store, but in the process of displaying the details of the channel in the store, the whole box freezes and reboots.
Can someone else give this a try? Just go to Netflix, then send the external control point POST to launch the channel store app to display the details of Hulu Plus (or any other app you may have on your Roku).
I can’t reproduce it, although I’m not running that exact firmware. Can you PM your serial number to me? Also, do you have Hulu Plus (the target in the Channel Store) installed when you do this?
So it turns out that the box only crashes if a dev app is installed while the external request is made.
Deleting a dev app “fixed” it. Adding the dev app back caused it to crash again (even though the dev app was in no way involved with the external control point request).
So this is not a “mass” issue, but definitely a bug Roku introduced with the new Channel Store UI in the latest firmware.
And, yes, the POST info was a valid HTTP 1.1 POST. I even used IE to do it with the same result.
And the box was in all cases replying back with a 200 OK response, and began to execute the launch of the Channel Store app.
It just crashed while painting the Channel Store screen (thumbnails were missing but most data was visible at the time of crash).
“roquoonewbie” wrote:
So it turns out that the box only crashes if a dev app is installed while the external request is made.
Deleting a dev app “fixed” it. Adding the dev app back caused it to crash again (even though the dev app was in no way involved with the external control point request).
I always have a dev app installed, including when I did the testing of the issue earlier in this thread. Are you seeing it with any dev app, or just a specific one?
