Hi,
I am uploading a new channel and it is failing automatic certification with error
"The use of ECP from within a channel is now prohibited."
I am not using ECP in my channel, before getting this error and looking into it I didn't even knew what ECP was.
I tried zip and squashfs file, both give the same error.
The channel code itself is pretty small, just a couple of files as this is my preliminary upload just to get the market page up and running.
Should I add something to a manifest to define that I am indeed not using this feature?
Thanks.
The static analysis scan is VERY primitive. You can think of it mostly as a regex scraper that looks for "patterns" in your code with zero actual context.
So if you're positive you're not using ECP in your app, then maybe look around for places where you're building URLs, storing integers, etc. Maybe they're getting tripped up when seeing ":8060" somewhere in your code? or /launch or some other string that matches what they have in the ECP docs.
https://developer.roku.com/en-ca/docs/developer-program/dev-tools/external-control-api.md
http://<IP of Roku>:8060/launch/[dev | channeID]?contentId=<content ID>&MediaType=<mediaType>
Have you tried running the static analysis tool locally to see if you can reproduce the errors there? Might help you more quickly discover the place in code that's tripping up the rule.
Are you trying to make a HTTP connection to 127.0.0.1 or localhost within the channel?
The static analysis scan is VERY primitive. You can think of it mostly as a regex scraper that looks for "patterns" in your code with zero actual context.
So if you're positive you're not using ECP in your app, then maybe look around for places where you're building URLs, storing integers, etc. Maybe they're getting tripped up when seeing ":8060" somewhere in your code? or /launch or some other string that matches what they have in the ECP docs.
https://developer.roku.com/en-ca/docs/developer-program/dev-tools/external-control-api.md
http://<IP of Roku>:8060/launch/[dev | channeID]?contentId=<content ID>&MediaType=<mediaType>
Have you tried running the static analysis tool locally to see if you can reproduce the errors there? Might help you more quickly discover the place in code that's tripping up the rule.
Thanks, this tool is a godsend. Apparently there was a comment left on an unused file with text `localhost` in it.
that is hilarious - the fact that S.C.A.T. still cannot tell Code from Comments