This was an intentional change from Roku ad people where abusing this to link to other apps and such. This violates there certification policy’s so it was blocked from within the device.
Hi Chris,
Thanks for your reply. Reasonably I can only in partial agree with your explanation and here's why:
Chris-DP wrote:... This violates there certification policy’s so it was blocked from within the device.
As mentioned, that kind of control is understandable for published channels in line with the certification policy which was notified time ago by Roku and the community is well aware. However, dev apps are primarily intended for testing and not to be published right away as such.
About the misemploy statement, please notice that all channel apps must pass static analysis before they can be published, therefore adding restraints for the dev channel app is non-sense.
ECP commands are a useful tool during the development phase, so hopefully Roku will waive soon this pointless limitation and reenable ECP commands within the device for in-app testing purposes (as it was before OS 12.0).
I've passed on this suggestion to the dev platform team, and this proposal is under consideration. They did not expect it to affect in-app testing. In the meantime, you could use a webserver on your local machine as a proxy to connect back to ECP so you're not making a local connection from the device.
RokuBen Hi Ben,
Could you give us a feedback, please? Is there an OS update in progress to solve this limitation?
It has been over two months since the suggestion was passed to the dev platform team and so far the same limitation is still affecting in-app testing when trying to use an ECP command from the roku device with OS 12.0
It looks like this change won't be reverted. The security team didn't want to leave this mechanism open, even for sideloaded applications.
