when I have used curl to contact my roku boxes prior to today, the results have been the same no matter whether the address was written as ${ROKU_IP}/plugin_package or http://${ROKU_IP}/plugin_package. starting today, however, (or potentially even earlier, since I haven't sideloaded a new app in the ~two days before this) curl fails to successfully contact the device unless the schema is included in the address or the port is explicitly specified. this means that the installation and packaging commands in this plugin are not working at all for me.
I don't know if this is due to an update to the roku OS or something else (could even be related to macos 10.15 I guess??), but the fix is pretty easy—just prepend http:// before the device IP when installing or packaging a channel.
when I have used curl to contact my roku boxes prior to today, the results have been the same no matter whether the address was written as
${ROKU_IP}/plugin_packageorhttp://${ROKU_IP}/plugin_package. starting today, however, (or potentially even earlier, since I haven't sideloaded a new app in the ~two days before this) curl fails to successfully contact the device unless the schema is included in the address or the port is explicitly specified. this means that the installation and packaging commands in this plugin are not working at all for me.I don't know if this is due to an update to the roku OS or something else (could even be related to macos 10.15 I guess??), but the fix is pretty easy—just prepend
http://before the device IP when installing or packaging a channel.